Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db0f6b1501dab1eca5abf1cc94ba5321ce56b0ef72c84b389b7d7af821a7e811

Tx prefix hash: cb40b52d4f6399328a2e59f6a4cdaaf15640e51dbab32fc3be9f0d424e310e4c
Tx public key: 496aa5c6631be175d9ebd6b499179bbb6ec26338a29742a57c78efd82228043e
Timestamp: 1722274445 Timestamp [UCT]: 2024-07-29 17:34:05 Age [y:d:h:m:s]: 00:253:06:42:15
Block: 1076405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180922 RingCT/type: yes/0
Extra: 01496aa5c6631be175d9ebd6b499179bbb6ec26338a29742a57c78efd82228043e02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 709e815be98d73c734c17d40494fd573b5a3fbd6e947967e40cf4f8302d1bed5 0.600000000000 1548942 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": 1076415, "vin": [ { "gen": { "height": 1076405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "709e815be98d73c734c17d40494fd573b5a3fbd6e947967e40cf4f8302d1bed5" } } ], "extra": [ 1, 73, 106, 165, 198, 99, 27, 225, 117, 217, 235, 214, 180, 153, 23, 155, 187, 110, 194, 99, 56, 162, 151, 66, 165, 124, 120, 239, 216, 34, 40, 4, 62, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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