Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 784dea186b6e4e4f6f18818c6795722394b11cfab8fe34022075468c6364d859

Tx prefix hash: 77538738088c4b2dd441aa0a488fa20b2d53c9f653137850d7961fd8d6080db1
Tx public key: c3c09ee5f8ee22a85667bcfb64f0e6f679cae4b8bd5ccf2a31e6c7fbc989e6cb
Timestamp: 1715173630 Timestamp [UCT]: 2024-05-08 13:07:10 Age [y:d:h:m:s]: 01:008:07:22:11
Block: 1017554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266851 RingCT/type: yes/0
Extra: 01c3c09ee5f8ee22a85667bcfb64f0e6f679cae4b8bd5ccf2a31e6c7fbc989e6cb02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 477054680bdcf1165817f402b3570108f314fd8c6129ee1c9534f17609fb9781 0.600000000000 1481337 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": 1017564, "vin": [ { "gen": { "height": 1017554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "477054680bdcf1165817f402b3570108f314fd8c6129ee1c9534f17609fb9781" } } ], "extra": [ 1, 195, 192, 158, 229, 248, 238, 34, 168, 86, 103, 188, 251, 100, 240, 230, 246, 121, 202, 228, 184, 189, 92, 207, 42, 49, 230, 199, 251, 201, 137, 230, 203, 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