Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8730d2f4f09068461a9bc632e718b3a6d1a6de0024af3a6add84f2fb03df8bd4

Tx prefix hash: ad65d4bf972dcea29c53dd32a75f98c3acff29091fb253959f017082d2678d86
Tx public key: 6dcdecb957233abef3df31df85a5b3deaeee09d853a0b5f47adab52754788ed0
Timestamp: 1715985188 Timestamp [UCT]: 2024-05-17 22:33:08 Age [y:d:h:m:s]: 00:326:00:29:35
Block: 1024271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233020 RingCT/type: yes/0
Extra: 016dcdecb957233abef3df31df85a5b3deaeee09d853a0b5f47adab52754788ed002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7aa1bfd35d420400f9ad8a18570a618c3fcc8f167e70278a37a5cc636b687659 0.600000000000 1489884 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": 1024281, "vin": [ { "gen": { "height": 1024271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7aa1bfd35d420400f9ad8a18570a618c3fcc8f167e70278a37a5cc636b687659" } } ], "extra": [ 1, 109, 205, 236, 185, 87, 35, 58, 190, 243, 223, 49, 223, 133, 165, 179, 222, 174, 238, 9, 216, 83, 160, 181, 244, 122, 218, 181, 39, 84, 120, 142, 208, 2, 17, 0, 0, 0, 1, 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