Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40cc707d745d673f45b7d3f91e9a5d872be08c034c8ee44d16b7cc054aed536f

Tx prefix hash: c5e0d806e90e1a8b3dff3e16606d27fffee99d2e28f338ba20616aa3808c68a8
Tx public key: 6d73e1eeee05dcb1781db8b92a82dce62f031255547d2226781c2b0a42b34cd5
Timestamp: 1702223183 Timestamp [UCT]: 2023-12-10 15:46:23 Age [y:d:h:m:s]: 01:183:07:31:42
Block: 910170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392208 RingCT/type: yes/0
Extra: 016d73e1eeee05dcb1781db8b92a82dce62f031255547d2226781c2b0a42b34cd502110000000433af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41d5d8c4971d53d6fc5e5d05078f4fa8bcff526901578a0d84310229cd497043 0.600000000000 1367315 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": 910180, "vin": [ { "gen": { "height": 910170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41d5d8c4971d53d6fc5e5d05078f4fa8bcff526901578a0d84310229cd497043" } } ], "extra": [ 1, 109, 115, 225, 238, 238, 5, 220, 177, 120, 29, 184, 185, 42, 130, 220, 230, 47, 3, 18, 85, 84, 125, 34, 38, 120, 28, 43, 10, 66, 179, 76, 213, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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