Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71d03b0c919f8c5bfc4ac03ce580fd743dbf2a11374b6874fc229fdb86210b7e

Tx prefix hash: 996637cace8ef0c5d70f795a0fa991da80bd9451d6cad8fc6988a9fc8d4eb7f6
Tx public key: 6348d5c8668f2c81f1f5affc5e042d864672ee5cbea87c61f534e10902437ad2
Timestamp: 1720275111 Timestamp [UCT]: 2024-07-06 14:11:51 Age [y:d:h:m:s]: 01:125:05:42:53
Block: 1059835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348029 RingCT/type: yes/0
Extra: 016348d5c8668f2c81f1f5affc5e042d864672ee5cbea87c61f534e10902437ad20211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 162f8b79623c21dec3e90bcff7538c6f59263eea576769368af8e543d1c12b56 0.600000000000 1530306 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": 1059845, "vin": [ { "gen": { "height": 1059835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "162f8b79623c21dec3e90bcff7538c6f59263eea576769368af8e543d1c12b56" } } ], "extra": [ 1, 99, 72, 213, 200, 102, 143, 44, 129, 241, 245, 175, 252, 94, 4, 45, 134, 70, 114, 238, 92, 190, 168, 124, 97, 245, 52, 225, 9, 2, 67, 122, 210, 2, 17, 0, 0, 0, 6, 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