Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc136599af43143f055be23a6bbde3eee82d65c5f5a844c9fe6a6182909ae8b

Tx prefix hash: 092c93187ebe32d80c85c9096027b742595db00f1155af14b0507e59597e3f95
Tx public key: 359d5676ad3c98faf59bf97d3d09dc72f0c84878e4a2b2168c16eaa07c5d2dd6
Timestamp: 1763849061 Timestamp [UCT]: 2025-11-22 22:04:21 Age [y:d:h:m:s]: 00:005:13:03:49
Block: 1417949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3976 RingCT/type: yes/0
Extra: 01359d5676ad3c98faf59bf97d3d09dc72f0c84878e4a2b2168c16eaa07c5d2dd6021100000007d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1ccde3c7675320f499448ee2d9c34ec093559294bcceff3db3d4f7876f41270 0.600000000000 1906476 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": 1417959, "vin": [ { "gen": { "height": 1417949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1ccde3c7675320f499448ee2d9c34ec093559294bcceff3db3d4f7876f41270" } } ], "extra": [ 1, 53, 157, 86, 118, 173, 60, 152, 250, 245, 155, 249, 125, 61, 9, 220, 114, 240, 200, 72, 120, 228, 162, 178, 22, 140, 22, 234, 160, 124, 93, 45, 214, 2, 17, 0, 0, 0, 7, 214, 225, 157, 124, 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