Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b72fce7613ee6fd1b37b87c636a64a2ceff3c719c69533a0383bd87b7e058e18

Tx prefix hash: 93d89ea74abc0e58b0c37a3f0b35a4f26f2206472acc8c12adf28a44ed39d819
Tx public key: c0cf5e7b3e7828cd665b6ca6f6b4bf5b04f048ed866588906bbb7fff50a3b300
Timestamp: 1694249637 Timestamp [UCT]: 2023-09-09 08:53:57 Age [y:d:h:m:s]: 01:213:01:40:18
Block: 844250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413393 RingCT/type: yes/0
Extra: 01c0cf5e7b3e7828cd665b6ca6f6b4bf5b04f048ed866588906bbb7fff50a3b30002110000000a33af99f4000000000000000000

1 output(s) for total of 0.978699463000 dcy

stealth address amount amount idx
00: bd79b2e5be0cfa39badddd2aed7bb89f31d6771c4ef7f103714e1fb1f2f5bbb9 0.978699463000 1297548 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 844260, "vin": [ { "gen": { "height": 844250 } } ], "vout": [ { "amount": 978699463, "target": { "key": "bd79b2e5be0cfa39badddd2aed7bb89f31d6771c4ef7f103714e1fb1f2f5bbb9" } } ], "extra": [ 1, 192, 207, 94, 123, 62, 120, 40, 205, 102, 91, 108, 166, 246, 180, 191, 91, 4, 240, 72, 237, 134, 101, 136, 144, 107, 187, 127, 255, 80, 163, 179, 0, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8