Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f3de91ec098ea7da936cb8c5a242cf325dcfc0a613579ba1f3d17a40fc2b18b

Tx prefix hash: 5ed5036e685cacd4156cd907c64587f15a9b94e1942655f5fa489ddb30e6ea57
Tx public key: 6e4d534eb69399dd8e4bcc444cd384183293a25a2917497d52bc9839d1b9befb
Timestamp: 1728468155 Timestamp [UCT]: 2024-10-09 10:02:35 Age [y:d:h:m:s]: 00:169:02:11:50
Block: 1127762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120623 RingCT/type: yes/0
Extra: 016e4d534eb69399dd8e4bcc444cd384183293a25a2917497d52bc9839d1b9befb02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68f3b12696a53f113d1442cb7b8808e4174f77bcd9d8933f43bbdb653d3ddd78 0.600000000000 1610573 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": 1127772, "vin": [ { "gen": { "height": 1127762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68f3b12696a53f113d1442cb7b8808e4174f77bcd9d8933f43bbdb653d3ddd78" } } ], "extra": [ 1, 110, 77, 83, 78, 182, 147, 153, 221, 142, 75, 204, 68, 76, 211, 132, 24, 50, 147, 162, 90, 41, 23, 73, 125, 82, 188, 152, 57, 209, 185, 190, 251, 2, 17, 0, 0, 0, 1, 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