Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ca813cec943838e9eb3b8319959a60908fb7659129e27ac4b9f78a6d6a43fc6

Tx prefix hash: c40cf60fe9b0fb7500cc5a1d22da5de3902183e89974ec5654a360efdc16b7d3
Tx public key: 6d78dcf4c8fbe079af7478cd2a70c865c997f0b82628432ca4aa910e6653d5ad
Timestamp: 1735095363 Timestamp [UCT]: 2024-12-25 02:56:03 Age [y:d:h:m:s]: 00:002:12:22:00
Block: 1182595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1777 RingCT/type: yes/0
Extra: 016d78dcf4c8fbe079af7478cd2a70c865c997f0b82628432ca4aa910e6653d5ad021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21597006b9f9d809678239d7b0c5be9016da826b176bf45c5280b16a3e7701d4 0.600000000000 1669030 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": 1182605, "vin": [ { "gen": { "height": 1182595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21597006b9f9d809678239d7b0c5be9016da826b176bf45c5280b16a3e7701d4" } } ], "extra": [ 1, 109, 120, 220, 244, 200, 251, 224, 121, 175, 116, 120, 205, 42, 112, 200, 101, 201, 151, 240, 184, 38, 40, 67, 44, 164, 170, 145, 14, 102, 83, 213, 173, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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