Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57823c62667a29acd879a6a78d6374149db42fb362c79527af6d14f338d9a9f6

Tx prefix hash: c8796efe1e26a88e2b0f6ec383ef8d0992f20bc0eb73459d4f60d2bd3ce8ff63
Tx public key: f4315acca460c2d2c13baf10b2ca19d74a4fcfff0e322f96338561f15ed316dc
Timestamp: 1715111041 Timestamp [UCT]: 2024-05-07 19:44:01 Age [y:d:h:m:s]: 00:336:22:47:40
Block: 1017028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240847 RingCT/type: yes/0
Extra: 01f4315acca460c2d2c13baf10b2ca19d74a4fcfff0e322f96338561f15ed316dc0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f47b7b03da004f6fbf00e80c28d9a2bff27ab4caa3f34505dc738e547c4ffb8f 0.600000000000 1480783 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": 1017038, "vin": [ { "gen": { "height": 1017028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f47b7b03da004f6fbf00e80c28d9a2bff27ab4caa3f34505dc738e547c4ffb8f" } } ], "extra": [ 1, 244, 49, 90, 204, 164, 96, 194, 210, 193, 59, 175, 16, 178, 202, 25, 215, 74, 79, 207, 255, 14, 50, 47, 150, 51, 133, 97, 241, 94, 211, 22, 220, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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