Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: accac2cf3eca6ed557f8da7360fdc400eb766392a8751efd207bcfcdd9d6e808

Tx prefix hash: 54fb3b15e08c0b98e40f340aded38730c0222aa168b4c3309a409683135d4dd8
Tx public key: cded45b4f2e8c091bcb2952b3e6639fd0b46e6913068bca61ef8a02bb9f92ab2
Timestamp: 1759581384 Timestamp [UCT]: 2025-10-04 12:36:24 Age [y:d:h:m:s]: 00:093:07:41:27
Block: 1382586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66841 RingCT/type: yes/0
Extra: 01cded45b4f2e8c091bcb2952b3e6639fd0b46e6913068bca61ef8a02bb9f92ab202110000000697baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22c94f415c9cee3fe41965be3e2d3335a24bb5d025c9daee518e56cf1f02cb80 0.600000000000 1870721 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": 1382596, "vin": [ { "gen": { "height": 1382586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22c94f415c9cee3fe41965be3e2d3335a24bb5d025c9daee518e56cf1f02cb80" } } ], "extra": [ 1, 205, 237, 69, 180, 242, 232, 192, 145, 188, 178, 149, 43, 62, 102, 57, 253, 11, 70, 230, 145, 48, 104, 188, 166, 30, 248, 160, 43, 185, 249, 42, 178, 2, 17, 0, 0, 0, 6, 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