Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f57ad5558739c8c7ccff208baf83604b743bc8df7e0167434c7155fb4d4107c

Tx prefix hash: 776a51cb6745d455c17ce04452874d21176bcdb873a4960e30786c938097fdf5
Tx public key: 697e9230b041177e8468ca24a62a44418a10c663d7ec3f2a271a7b2d5dc05238
Timestamp: 1703576717 Timestamp [UCT]: 2023-12-26 07:45:17 Age [y:d:h:m:s]: 01:330:17:54:20
Block: 921392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495226 RingCT/type: yes/0
Extra: 01697e9230b041177e8468ca24a62a44418a10c663d7ec3f2a271a7b2d5dc0523802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46f4e54156ef5aaab99812c7488e1cb76d61883a608fc255964805c29087f7a4 0.600000000000 1379080 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": 921402, "vin": [ { "gen": { "height": 921392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46f4e54156ef5aaab99812c7488e1cb76d61883a608fc255964805c29087f7a4" } } ], "extra": [ 1, 105, 126, 146, 48, 176, 65, 23, 126, 132, 104, 202, 36, 166, 42, 68, 65, 138, 16, 198, 99, 215, 236, 63, 42, 39, 26, 123, 45, 93, 192, 82, 56, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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