Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15a5022a8dff7646e18cf2139c2bf8aef04e7dae8415fafb66a83feb39102244

Tx prefix hash: 3c776e62ffc3c5fdab306c30a8108446e58adb420c00a1400094befa9fb0b9af
Tx public key: 85a1d0d39fd9c4be582186f58a1cc2d112671f266efac55a6ad7ba8aace66011
Timestamp: 1716679681 Timestamp [UCT]: 2024-05-25 23:28:01 Age [y:d:h:m:s]: 00:293:23:55:46
Block: 1030037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210139 RingCT/type: yes/0
Extra: 0185a1d0d39fd9c4be582186f58a1cc2d112671f266efac55a6ad7ba8aace660110211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b7d6fc7968edaa350ee91cbac8f50d613239b64e85ef7fc0fcb08de28c129d5 0.600000000000 1498286 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": 1030047, "vin": [ { "gen": { "height": 1030037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b7d6fc7968edaa350ee91cbac8f50d613239b64e85ef7fc0fcb08de28c129d5" } } ], "extra": [ 1, 133, 161, 208, 211, 159, 217, 196, 190, 88, 33, 134, 245, 138, 28, 194, 209, 18, 103, 31, 38, 110, 250, 197, 90, 106, 215, 186, 138, 172, 230, 96, 17, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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