Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca2ae30b8e452fc2c04aee9c6594e86e5ae172d946aafd6c2f55963fbf5ca6d8

Tx prefix hash: 88363c9aae55082d9cb6427973b365707061ab58a86607710336e1b99ae46f07
Tx public key: 76796c4152975ec227c9cfbcc566a6764613abb08581dc343e798b0a28531c2e
Timestamp: 1714967466 Timestamp [UCT]: 2024-05-06 03:51:06 Age [y:d:h:m:s]: 00:343:21:07:12
Block: 1015840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245807 RingCT/type: yes/0
Extra: 0176796c4152975ec227c9cfbcc566a6764613abb08581dc343e798b0a28531c2e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7413ffed27430884c0cd8a0533e6ac058c719b3a9601575fd9dce4dbf68fd2aa 0.600000000000 1479283 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": 1015850, "vin": [ { "gen": { "height": 1015840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7413ffed27430884c0cd8a0533e6ac058c719b3a9601575fd9dce4dbf68fd2aa" } } ], "extra": [ 1, 118, 121, 108, 65, 82, 151, 94, 194, 39, 201, 207, 188, 197, 102, 166, 118, 70, 19, 171, 176, 133, 129, 220, 52, 62, 121, 139, 10, 40, 83, 28, 46, 2, 17, 0, 0, 0, 1, 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