Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e95f563e0ac4fbb9ee70e8e06506c4794102d04445cdf2ecf855a4244c631737

Tx prefix hash: a0d78bd7116799be8b8dc4f82b92775d941e065bcd954e94eaf8339bff9861d0
Tx public key: f867c15d78391424b5c7c4fe5cd0a888aafa7aed2cd0096f3e1755fa29ce7ef6
Timestamp: 1677089775 Timestamp [UCT]: 2023-02-22 18:16:15 Age [y:d:h:m:s]: 02:003:00:25:43
Block: 702689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523708 RingCT/type: yes/0
Extra: 01f867c15d78391424b5c7c4fe5cd0a888aafa7aed2cd0096f3e1755fa29ce7ef602110000000174b6d784000000000000000000

1 output(s) for total of 2.882037001000 dcy

stealth address amount amount idx
00: 5bea4fc31efee3194e85f97288452546ff5121a2184a6201d5317a7e6e9a6c76 2.882037001000 1146228 of 0

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": 702699, "vin": [ { "gen": { "height": 702689 } } ], "vout": [ { "amount": 2882037001, "target": { "key": "5bea4fc31efee3194e85f97288452546ff5121a2184a6201d5317a7e6e9a6c76" } } ], "extra": [ 1, 248, 103, 193, 93, 120, 57, 20, 36, 181, 199, 196, 254, 92, 208, 168, 136, 170, 250, 122, 237, 44, 208, 9, 111, 62, 23, 85, 250, 41, 206, 126, 246, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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