Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c582b8abe6c3aab34864b4317f668f1600132b3bde7485a5fd346a7d20d8588a

Tx prefix hash: ee1a220a4670b54319bb09733b8eef73f9e191d1f1da7c29626da523696fe057
Tx public key: 4253c874a0e39ab160c96baba2f53aa8529b9832d18ebf8e6144a34ea426cb25
Timestamp: 1702696349 Timestamp [UCT]: 2023-12-16 03:12:29 Age [y:d:h:m:s]: 01:036:00:57:43
Block: 914097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287078 RingCT/type: yes/0
Extra: 014253c874a0e39ab160c96baba2f53aa8529b9832d18ebf8e6144a34ea426cb2502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffa9bdc67be6a5c431b7a0eb5a5fe2cc19d95de3ee513a871df15e02228d4726 0.600000000000 1371381 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": 914107, "vin": [ { "gen": { "height": 914097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffa9bdc67be6a5c431b7a0eb5a5fe2cc19d95de3ee513a871df15e02228d4726" } } ], "extra": [ 1, 66, 83, 200, 116, 160, 227, 154, 177, 96, 201, 107, 171, 162, 245, 58, 168, 82, 155, 152, 50, 209, 142, 191, 142, 97, 68, 163, 78, 164, 38, 203, 37, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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