Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fa920821cd262ec93556eb0463e40359c7de3f2da8e5c4a65e380d8f4dad8c7

Tx prefix hash: 4abcf026626d238adabe1be802c6fea29eaf7cd40e13b352daf8a530027eff33
Tx public key: ad88b1c73a8530f0c07077d39e0dd90b19e5178130bdb57bc4f0d4385d404e6e
Timestamp: 1733374331 Timestamp [UCT]: 2024-12-05 04:52:11 Age [y:d:h:m:s]: 00:114:00:57:07
Block: 1168335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81303 RingCT/type: yes/0
Extra: 01ad88b1c73a8530f0c07077d39e0dd90b19e5178130bdb57bc4f0d4385d404e6e0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 136fa41cf90a6cf5ffc96eb9f082462c21e86e9060a28df985c5bf0ce0ce7ebf 0.600000000000 1654044 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": 1168345, "vin": [ { "gen": { "height": 1168335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "136fa41cf90a6cf5ffc96eb9f082462c21e86e9060a28df985c5bf0ce0ce7ebf" } } ], "extra": [ 1, 173, 136, 177, 199, 58, 133, 48, 240, 192, 112, 119, 211, 158, 13, 217, 11, 25, 229, 23, 129, 48, 189, 181, 123, 196, 240, 212, 56, 93, 64, 78, 110, 2, 17, 0, 0, 0, 6, 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