Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5712972e97996b12fc5addd4a5248c1e0ac8f93eddc04b2985c5d344b6bd11b0

Tx prefix hash: eee9629dc0013eabc4d213c087a8dc574e342e027a1290c78a2ac66b898aa890
Tx public key: bedb31d1c97d6a1862e7010f0571f0d0c47758332a81c32bcc4ca03852279235
Timestamp: 1719602780 Timestamp [UCT]: 2024-06-28 19:26:20 Age [y:d:h:m:s]: 00:277:07:38:59
Block: 1054253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198144 RingCT/type: yes/0
Extra: 01bedb31d1c97d6a1862e7010f0571f0d0c47758332a81c32bcc4ca0385227923502110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 001a72c31ebe293aa007534fe5e2ca1a032fd1a5e29f10f87f88bb577dc6da4b 0.600000000000 1524614 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": 1054263, "vin": [ { "gen": { "height": 1054253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "001a72c31ebe293aa007534fe5e2ca1a032fd1a5e29f10f87f88bb577dc6da4b" } } ], "extra": [ 1, 190, 219, 49, 209, 201, 125, 106, 24, 98, 231, 1, 15, 5, 113, 240, 208, 196, 119, 88, 51, 42, 129, 195, 43, 204, 76, 160, 56, 82, 39, 146, 53, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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