Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c9e683785dd8913be64353782b2e324d6d3afc0739c8d728f4dc12795a2901c

Tx prefix hash: e04b7b2cdadae6c7e639b5e230472c9a3e08085e633ff97713d7f672289ab4cd
Tx public key: a974f0165c0d7e341ae84c9374fd8ca5434439c4fc16be31f4ab43912ee1c42b
Timestamp: 1714408469 Timestamp [UCT]: 2024-04-29 16:34:29 Age [y:d:h:m:s]: 00:272:12:54:33
Block: 1011198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194824 RingCT/type: yes/0
Extra: 01a974f0165c0d7e341ae84c9374fd8ca5434439c4fc16be31f4ab43912ee1c42b0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7ca5705fa86205266717dc7a314bb821d991a5e927c2003786b309e202b0cfd 0.600000000000 1473366 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": 1011208, "vin": [ { "gen": { "height": 1011198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7ca5705fa86205266717dc7a314bb821d991a5e927c2003786b309e202b0cfd" } } ], "extra": [ 1, 169, 116, 240, 22, 92, 13, 126, 52, 26, 232, 76, 147, 116, 253, 140, 165, 67, 68, 57, 196, 252, 22, 190, 49, 244, 171, 67, 145, 46, 225, 196, 43, 2, 17, 0, 0, 0, 6, 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