Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f0b7c882e026e3af03b56afa4397fac8447a877feaff60e69be26fdf46851a8

Tx prefix hash: e6ce62fec6aeba522c1e2b62de745884f92468896e4493b2899ca3cb75c2a15a
Tx public key: 0d4a4cf56ac22da14a0d31db9657a2f8c03a5b2cf7842ad057d7662a98438e6f
Timestamp: 1712186756 Timestamp [UCT]: 2024-04-03 23:25:56 Age [y:d:h:m:s]: 01:006:13:17:15
Block: 992749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265673 RingCT/type: yes/0
Extra: 010d4a4cf56ac22da14a0d31db9657a2f8c03a5b2cf7842ad057d7662a98438e6f0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b69074a6cba4706fc2c5fe08adbf39df0038b4855e94bd55f8e06d3a11d542c8 0.600000000000 1453123 of 15

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": 992759, "vin": [ { "gen": { "height": 992749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b69074a6cba4706fc2c5fe08adbf39df0038b4855e94bd55f8e06d3a11d542c8" } } ], "extra": [ 1, 13, 74, 76, 245, 106, 194, 45, 161, 74, 13, 49, 219, 150, 87, 162, 248, 192, 58, 91, 44, 247, 132, 42, 208, 87, 215, 102, 42, 152, 67, 142, 111, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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