Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 348a575e0f9b37463abcbab847ce3edf3d4114dde016df5443aa427e0ef55ab8

Tx prefix hash: 8aea13079282aed12583aab96da4cf9c26d07d82d910961218319350680e94b8
Tx public key: 9bb3a5eb4a7c811b889b21bb403914b9a2dfc3c329a5d490b263183a91964520
Timestamp: 1698569540 Timestamp [UCT]: 2023-10-29 08:52:20 Age [y:d:h:m:s]: 01:117:14:43:08
Block: 880104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345003 RingCT/type: yes/0
Extra: 019bb3a5eb4a7c811b889b21bb403914b9a2dfc3c329a5d490b263183a919645200211000000024b8f5122000000000000000000

1 output(s) for total of 0.744474989000 dcy

stealth address amount amount idx
00: 05f71b76d53fcd7a7169e471ceeb8ab3a7b031611c66d9f89e2178fe55a9bd44 0.744474989000 1335646 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": 880114, "vin": [ { "gen": { "height": 880104 } } ], "vout": [ { "amount": 744474989, "target": { "key": "05f71b76d53fcd7a7169e471ceeb8ab3a7b031611c66d9f89e2178fe55a9bd44" } } ], "extra": [ 1, 155, 179, 165, 235, 74, 124, 129, 27, 136, 155, 33, 187, 64, 57, 20, 185, 162, 223, 195, 195, 41, 165, 212, 144, 178, 99, 24, 58, 145, 150, 69, 32, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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