Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49e117aae3170381cf85e98904ca0a3f0fa50930696b876019974e08d8324f01

Tx prefix hash: e826e8456fef022b7492d7b8d38fbd9f8861fe6c38e0745d6209c18a8c9792c2
Tx public key: b9258178a19dd187a2b907fdf96a8a9db145a020bcb84b537b155f5d33a1474e
Timestamp: 1759097272 Timestamp [UCT]: 2025-09-28 22:07:52 Age [y:d:h:m:s]: 00:124:07:29:15
Block: 1378566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88832 RingCT/type: yes/0
Extra: 01b9258178a19dd187a2b907fdf96a8a9db145a020bcb84b537b155f5d33a1474e02110000000397baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cfe6f0f0ff8b92eec2eb0f521c6d8975a21a54658e883b24f593f57434b16fa 0.600000000000 1866661 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": 1378576, "vin": [ { "gen": { "height": 1378566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cfe6f0f0ff8b92eec2eb0f521c6d8975a21a54658e883b24f593f57434b16fa" } } ], "extra": [ 1, 185, 37, 129, 120, 161, 157, 209, 135, 162, 185, 7, 253, 249, 106, 138, 157, 177, 69, 160, 32, 188, 184, 75, 83, 123, 21, 95, 93, 51, 161, 71, 78, 2, 17, 0, 0, 0, 3, 151, 186, 249, 34, 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