Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f9bc865f77fa4e73f8350add41a706e1a1c529c3b3c8cc9f2919cdd5a3f988c

Tx prefix hash: 296fd0889e429d79276df4a1fefe43f4597baaf7456df9cb16a00e34cc4f1372
Tx public key: 9d3400d3146bf22434a5931277062d656753bd9a95ddc0ac6605d95b72f98015
Timestamp: 1719371802 Timestamp [UCT]: 2024-06-26 03:16:42 Age [y:d:h:m:s]: 00:264:09:12:46
Block: 1052338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188931 RingCT/type: yes/0
Extra: 019d3400d3146bf22434a5931277062d656753bd9a95ddc0ac6605d95b72f980150211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47d0b3d0f8e5368616f705cbacf28b46863bf4f59e48f933f5b22d919e97455f 0.600000000000 1522661 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": 1052348, "vin": [ { "gen": { "height": 1052338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47d0b3d0f8e5368616f705cbacf28b46863bf4f59e48f933f5b22d919e97455f" } } ], "extra": [ 1, 157, 52, 0, 211, 20, 107, 242, 36, 52, 165, 147, 18, 119, 6, 45, 101, 103, 83, 189, 154, 149, 221, 192, 172, 102, 5, 217, 91, 114, 249, 128, 21, 2, 17, 0, 0, 0, 9, 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