Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95991f7be105f17ae937e4c34cd9760cc934ddcc5c741f45561962b59cc83dfe

Tx prefix hash: 11e87df759c165737a18c05248df2f47d39700ddb5100fbe98c45e7254d9c9b1
Tx public key: 5f7a408dca605bc42ecb16cbf99b23409e59df3474401e4db7a3a32957fb6ac2
Timestamp: 1723919572 Timestamp [UCT]: 2024-08-17 18:32:52 Age [y:d:h:m:s]: 00:232:10:46:48
Block: 1090058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165984 RingCT/type: yes/0
Extra: 015f7a408dca605bc42ecb16cbf99b23409e59df3474401e4db7a3a32957fb6ac202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 348567393a7b86611c11d75a6b16d6d1a293ec41bf24ac0a07515e6a9a715e11 0.600000000000 1564681 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": 1090068, "vin": [ { "gen": { "height": 1090058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "348567393a7b86611c11d75a6b16d6d1a293ec41bf24ac0a07515e6a9a715e11" } } ], "extra": [ 1, 95, 122, 64, 141, 202, 96, 91, 196, 46, 203, 22, 203, 249, 155, 35, 64, 158, 89, 223, 52, 116, 64, 30, 77, 183, 163, 163, 41, 87, 251, 106, 194, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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