Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 769234ea410e83692dbbb542b1aa4828b1c5a42ce9bf83bc4f7b7e2a10e377a5

Tx prefix hash: ddba4c4b2f424d16427cb1379894d573ee97b9282a1a33bd078d5eb1123fad3b
Tx public key: a8f8bb1c1012e77e90c89f3acfd02a7b5f26eea35bb811ae7320e62ceb0ef848
Timestamp: 1734483576 Timestamp [UCT]: 2024-12-18 00:59:36 Age [y:d:h:m:s]: 00:022:21:12:04
Block: 1177547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16341 RingCT/type: yes/0
Extra: 01a8f8bb1c1012e77e90c89f3acfd02a7b5f26eea35bb811ae7320e62ceb0ef8480211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7d0d19724eec6ff8ed30987b9db6c66e569773dc0a28cc05f5fae6eeb36e5e0 0.600000000000 1663918 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": 1177557, "vin": [ { "gen": { "height": 1177547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7d0d19724eec6ff8ed30987b9db6c66e569773dc0a28cc05f5fae6eeb36e5e0" } } ], "extra": [ 1, 168, 248, 187, 28, 16, 18, 231, 126, 144, 200, 159, 58, 207, 208, 42, 123, 95, 38, 238, 163, 91, 184, 17, 174, 115, 32, 230, 44, 235, 14, 248, 72, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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