Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8a36d48449e74da7d9bdfcd593748306b122c97760ddc55a472fd796fc23f89

Tx prefix hash: f3f46b7d5ec7ed90a494bce950c323129d30052ce7226bf3595ef858ca9d90ee
Tx public key: e00ff3d759ff5003bd2bd212e1f7e52f5d42f53fbfeddc5b0911f5980e47e2f2
Timestamp: 1737543469 Timestamp [UCT]: 2025-01-22 10:57:49 Age [y:d:h:m:s]: 00:302:08:25:38
Block: 1202807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213634 RingCT/type: yes/0
Extra: 01e00ff3d759ff5003bd2bd212e1f7e52f5d42f53fbfeddc5b0911f5980e47e2f2021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9516c8e88fc59e442b1931f817265b908f5e4d530078914c83b480bae2a8cab9 0.600000000000 1689474 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": 1202817, "vin": [ { "gen": { "height": 1202807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9516c8e88fc59e442b1931f817265b908f5e4d530078914c83b480bae2a8cab9" } } ], "extra": [ 1, 224, 15, 243, 215, 89, 255, 80, 3, 189, 43, 210, 18, 225, 247, 229, 47, 93, 66, 245, 63, 191, 237, 220, 91, 9, 17, 245, 152, 14, 71, 226, 242, 2, 17, 0, 0, 0, 7, 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