Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99e3db8b5d363967a1ab662d0b6637897b7afab4fc172c241537203e79ca2f29

Tx prefix hash: 37e697848e45c334705b44c0fe145d35bb43eafc67c6fee2162b1ca5c4ba9fd8
Tx public key: 6f8ea66152258a4c189eb13305c4ae088f48bde6d0f4e231dff3f2ebdac13bc7
Timestamp: 1703829629 Timestamp [UCT]: 2023-12-29 06:00:29 Age [y:d:h:m:s]: 01:316:03:13:18
Block: 923489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484777 RingCT/type: yes/0
Extra: 016f8ea66152258a4c189eb13305c4ae088f48bde6d0f4e231dff3f2ebdac13bc70211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2ecb1fedfe855ff3cb72009af5ad42e9e68890579563aff3796b4f05e2ee0a7 0.600000000000 1381221 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": 923499, "vin": [ { "gen": { "height": 923489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2ecb1fedfe855ff3cb72009af5ad42e9e68890579563aff3796b4f05e2ee0a7" } } ], "extra": [ 1, 111, 142, 166, 97, 82, 37, 138, 76, 24, 158, 177, 51, 5, 196, 174, 8, 143, 72, 189, 230, 208, 244, 226, 49, 223, 243, 242, 235, 218, 193, 59, 199, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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