Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6db1382d06c08d9f0047f865759a1f4b1389f64e4d1e4f0887a3a596de84621

Tx prefix hash: 42394c039ad204a49ce09b1c7c1861455e2d32f1446216a3c04f1caeea3b17e7
Tx public key: d8ae3ee118b829b27b9647f833352d983a14140fe02a85e132ed1ca4ae2fae59
Timestamp: 1704491176 Timestamp [UCT]: 2024-01-05 21:46:16 Age [y:d:h:m:s]: 01:051:04:16:28
Block: 928959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297651 RingCT/type: yes/0
Extra: 01d8ae3ee118b829b27b9647f833352d983a14140fe02a85e132ed1ca4ae2fae59021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b32fe043320f749148cade81035425e4f4cdc86408dec392b8b2a6ed9291bbfe 0.600000000000 1386825 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": 928969, "vin": [ { "gen": { "height": 928959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b32fe043320f749148cade81035425e4f4cdc86408dec392b8b2a6ed9291bbfe" } } ], "extra": [ 1, 216, 174, 62, 225, 24, 184, 41, 178, 123, 150, 71, 248, 51, 53, 45, 152, 58, 20, 20, 15, 224, 42, 133, 225, 50, 237, 28, 164, 174, 47, 174, 89, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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