Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ed9935348dec451b9125c2703fdd4b1e7def2cbb6a97151bdfaaaa6515aa1c7

Tx prefix hash: 9b71cb33b387137cea5e15e33c4b29f465ca1eccc79362e5d4565f4f6310ea15
Tx public key: e070ea641f5f504144c30eaaaf4a58d4b450f9df634517039c219981034986b0
Timestamp: 1736905441 Timestamp [UCT]: 2025-01-15 01:44:01 Age [y:d:h:m:s]: 00:154:18:44:55
Block: 1197556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110328 RingCT/type: yes/0
Extra: 01e070ea641f5f504144c30eaaaf4a58d4b450f9df634517039c219981034986b0021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7ad333bb70ad0d5d5155e3e3c61b88fca56a7872e8ea6e575b98d3be40ccba2 0.600000000000 1684169 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": 1197566, "vin": [ { "gen": { "height": 1197556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7ad333bb70ad0d5d5155e3e3c61b88fca56a7872e8ea6e575b98d3be40ccba2" } } ], "extra": [ 1, 224, 112, 234, 100, 31, 95, 80, 65, 68, 195, 14, 170, 175, 74, 88, 212, 180, 80, 249, 223, 99, 69, 23, 3, 156, 33, 153, 129, 3, 73, 134, 176, 2, 17, 0, 0, 0, 4, 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