Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 072d4a7903efdbea2eadbea791cc39a8c3a2861fe9cda0f0b153b6948c93dc94

Tx prefix hash: c7a93df1f8d6dd366aec18161c04092d2bbc0eda5f1dc2b7aa6651dd4e2ae584
Tx public key: e29867eaec5939b4a576870a63e2a9d0500ac40a9f4876eeac3965916177bd56
Timestamp: 1736165960 Timestamp [UCT]: 2025-01-06 12:19:20 Age [y:d:h:m:s]: 00:091:18:43:45
Block: 1191452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65362 RingCT/type: yes/0
Extra: 01e29867eaec5939b4a576870a63e2a9d0500ac40a9f4876eeac3965916177bd5602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ae33444926419deef18fd7917187f57f058800dd1582ea0a7df0976d88c5345 0.600000000000 1677991 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": 1191462, "vin": [ { "gen": { "height": 1191452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ae33444926419deef18fd7917187f57f058800dd1582ea0a7df0976d88c5345" } } ], "extra": [ 1, 226, 152, 103, 234, 236, 89, 57, 180, 165, 118, 135, 10, 99, 226, 169, 208, 80, 10, 196, 10, 159, 72, 118, 238, 172, 57, 101, 145, 97, 119, 189, 86, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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