Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60b6b6a889c18207255a2d551e0f9c11e07d25491f633d29d3cd5f25d55be7c9

Tx prefix hash: f4da05d120a8eccd4a8c8fd42def6ad5a40a03adfd523deec2395aff39bd7067
Tx public key: 92396657f2a0e9061055a0ede7621d817e1bdd8cbe0a5f2f104faf2ff616403b
Timestamp: 1717270642 Timestamp [UCT]: 2024-06-01 19:37:22 Age [y:d:h:m:s]: 00:294:04:32:53
Block: 1034934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210246 RingCT/type: yes/0
Extra: 0192396657f2a0e9061055a0ede7621d817e1bdd8cbe0a5f2f104faf2ff616403b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6b53b8667c85cda0f3cb833de66cff6d34945b78fa0a5cfe5f2abdb8cdd9e14 0.600000000000 1503453 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": 1034944, "vin": [ { "gen": { "height": 1034934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6b53b8667c85cda0f3cb833de66cff6d34945b78fa0a5cfe5f2abdb8cdd9e14" } } ], "extra": [ 1, 146, 57, 102, 87, 242, 160, 233, 6, 16, 85, 160, 237, 231, 98, 29, 129, 126, 27, 221, 140, 190, 10, 95, 47, 16, 79, 175, 47, 246, 22, 64, 59, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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