Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f98f023ff176b26addfe445d811971f0c900aec7c462947ff597d195e2af5a1

Tx prefix hash: 8ce226b3bd267015082598305f075b579a9c409a5494e513f66f95447dda1ccd
Tx public key: a904e022d24b26921b8e8f0ede013d69f1de3f4bf47af7c2fc991a1916109e45
Timestamp: 1707881756 Timestamp [UCT]: 2024-02-14 03:35:56 Age [y:d:h:m:s]: 01:040:12:59:08
Block: 957074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290014 RingCT/type: yes/0
Extra: 01a904e022d24b26921b8e8f0ede013d69f1de3f4bf47af7c2fc991a1916109e450211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 914979791748e6a445b40066931015f1145169cccfa0646cbc2e1fcddd23b6a9 0.600000000000 1416388 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": 957084, "vin": [ { "gen": { "height": 957074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "914979791748e6a445b40066931015f1145169cccfa0646cbc2e1fcddd23b6a9" } } ], "extra": [ 1, 169, 4, 224, 34, 210, 75, 38, 146, 27, 142, 143, 14, 222, 1, 61, 105, 241, 222, 63, 75, 244, 122, 247, 194, 252, 153, 26, 25, 22, 16, 158, 69, 2, 17, 0, 0, 0, 8, 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