Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34f62862ca057c4219dec0a70348db6521dced03d8d322145be851b8626cc1b2

Tx prefix hash: 900b73e370f360c1c1268a902664099998e16537a8a2efd44e5989ec26a8a6e7
Tx public key: 17db3b00d32a62b3af90858fb74a3ff90802d3ff8c6f93d7c7e6730f109bfb0a
Timestamp: 1735798948 Timestamp [UCT]: 2025-01-02 06:22:28 Age [y:d:h:m:s]: 00:172:08:52:08
Block: 1188405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122794 RingCT/type: yes/0
Extra: 0117db3b00d32a62b3af90858fb74a3ff90802d3ff8c6f93d7c7e6730f109bfb0a021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b8ec651bd937ca147ea5ec4dcc70d1f9d9f2ca5549d70733401f6227a28915e 0.600000000000 1674906 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": 1188415, "vin": [ { "gen": { "height": 1188405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b8ec651bd937ca147ea5ec4dcc70d1f9d9f2ca5549d70733401f6227a28915e" } } ], "extra": [ 1, 23, 219, 59, 0, 211, 42, 98, 179, 175, 144, 133, 143, 183, 74, 63, 249, 8, 2, 211, 255, 140, 111, 147, 215, 199, 230, 115, 15, 16, 155, 251, 10, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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