Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cc429455fc02d822cba72507607e6d3afa2cd07b56d26af7fd76700fefbcc18

Tx prefix hash: 23d6295f1165750a52397ac3eb769784c8022995357c5c2c0202a3488dd4a5b1
Tx public key: 8c67e118b0063b97b98a718e9ad97cb362008f2da5f8b9f16e806cbaf34558d9
Timestamp: 1714442390 Timestamp [UCT]: 2024-04-30 01:59:50 Age [y:d:h:m:s]: 00:326:22:27:04
Block: 1011472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233714 RingCT/type: yes/0
Extra: 018c67e118b0063b97b98a718e9ad97cb362008f2da5f8b9f16e806cbaf34558d90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94502c3030eee3ec7a6be76e1aa4ba4a55546e685dbb702af310f285282bd6d3 0.600000000000 1473714 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": 1011482, "vin": [ { "gen": { "height": 1011472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94502c3030eee3ec7a6be76e1aa4ba4a55546e685dbb702af310f285282bd6d3" } } ], "extra": [ 1, 140, 103, 225, 24, 176, 6, 59, 151, 185, 138, 113, 142, 154, 217, 124, 179, 98, 0, 143, 45, 165, 248, 185, 241, 110, 128, 108, 186, 243, 69, 88, 217, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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