Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b974a70cbba3ba1430f47559ebe9e521d1b92dcf8e08d9b0b034f9d7c165fa1

Tx prefix hash: bdc2c763b3e8d993a81a4bf1baf04c973a9e7b0beb0740aed034a3e8794495b5
Tx public key: f75812be6c706a933711b3468d92af310d37e9b954b4e9fadc80198a94b72855
Timestamp: 1716178956 Timestamp [UCT]: 2024-05-20 04:22:36 Age [y:d:h:m:s]: 00:325:09:16:36
Block: 1025885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232568 RingCT/type: yes/0
Extra: 01f75812be6c706a933711b3468d92af310d37e9b954b4e9fadc80198a94b7285502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f89660124da4e5d0ada6d05dc2afdac6031e78329beb4cff83d0d567c09974fb 0.600000000000 1492660 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": 1025895, "vin": [ { "gen": { "height": 1025885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f89660124da4e5d0ada6d05dc2afdac6031e78329beb4cff83d0d567c09974fb" } } ], "extra": [ 1, 247, 88, 18, 190, 108, 112, 106, 147, 55, 17, 179, 70, 141, 146, 175, 49, 13, 55, 233, 185, 84, 180, 233, 250, 220, 128, 25, 138, 148, 183, 40, 85, 2, 17, 0, 0, 0, 3, 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