Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2370f74069b610b769f612c62113f9a16494f620ce3f10019233a3a6f511caf4

Tx prefix hash: a566009b91d98b6cefb3181057d01680366d07bd9a5c08b5ed7635069aeaea8c
Tx public key: b01f00a096cffb417839d6979eefb109d087728855eae93545a9a97d155ade2c
Timestamp: 1728806240 Timestamp [UCT]: 2024-10-13 07:57:20 Age [y:d:h:m:s]: 00:251:04:08:10
Block: 1130568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179170 RingCT/type: yes/0
Extra: 01b01f00a096cffb417839d6979eefb109d087728855eae93545a9a97d155ade2c02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d5aa72dcd424d16fa86ca9a0bcdb267426e690ae8c6cd010e6b7ec3a4130c42 0.600000000000 1613445 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": 1130578, "vin": [ { "gen": { "height": 1130568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d5aa72dcd424d16fa86ca9a0bcdb267426e690ae8c6cd010e6b7ec3a4130c42" } } ], "extra": [ 1, 176, 31, 0, 160, 150, 207, 251, 65, 120, 57, 214, 151, 158, 239, 177, 9, 208, 135, 114, 136, 85, 234, 233, 53, 69, 169, 169, 125, 21, 90, 222, 44, 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