Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f45af9f82743db7aed19a59e26c13252142867bdb970b514572b5af0f2dbe52

Tx prefix hash: d969fc9aba3c79bc399348bac7caeb8bfb1914aa4737d99d56ca864be67b38ab
Tx public key: 7fb8ce4f1ce29cecbcec63b7ca70cc1d1d86dbe774e83ea3e1a39e31fe243ab1
Timestamp: 1714495605 Timestamp [UCT]: 2024-04-30 16:46:45 Age [y:d:h:m:s]: 01:191:05:39:00
Block: 1011925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395310 RingCT/type: yes/0
Extra: 017fb8ce4f1ce29cecbcec63b7ca70cc1d1d86dbe774e83ea3e1a39e31fe243ab10211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80ce322e33c00ffc2a6b7119dfeff31b628afcfb318312fcac6d379f0c67e781 0.600000000000 1474287 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": 1011935, "vin": [ { "gen": { "height": 1011925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80ce322e33c00ffc2a6b7119dfeff31b628afcfb318312fcac6d379f0c67e781" } } ], "extra": [ 1, 127, 184, 206, 79, 28, 226, 156, 236, 188, 236, 99, 183, 202, 112, 204, 29, 29, 134, 219, 231, 116, 232, 62, 163, 225, 163, 158, 49, 254, 36, 58, 177, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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