Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c4821dd5af479c8dd91fd3c7faa74417fc4ff432f615f87260c7677048674cd

Tx prefix hash: a2d9b5ff6d033703b7be6bad296baa2a118fe58f33bd3e3832f8ef7fdb3daf48
Tx public key: c4244cc9bac4d47fbd17173ffec22413e1bf373c96bb5ee6fb4e496cb91bffdf
Timestamp: 1671956205 Timestamp [UCT]: 2022-12-25 08:16:45 Age [y:d:h:m:s]: 02:138:06:58:56
Block: 660124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 620551 RingCT/type: yes/0
Extra: 01c4244cc9bac4d47fbd17173ffec22413e1bf373c96bb5ee6fb4e496cb91bffdf0211000000047e406890000000000000000000

1 output(s) for total of 3.987816162000 dcy

stealth address amount amount idx
00: 935e216f714c7e846b82a563ff1b5d12a3a66be79beb659fde333c024fe61008 3.987816162000 1100853 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": 660134, "vin": [ { "gen": { "height": 660124 } } ], "vout": [ { "amount": 3987816162, "target": { "key": "935e216f714c7e846b82a563ff1b5d12a3a66be79beb659fde333c024fe61008" } } ], "extra": [ 1, 196, 36, 76, 201, 186, 196, 212, 127, 189, 23, 23, 63, 254, 194, 36, 19, 225, 191, 55, 60, 150, 187, 94, 230, 251, 78, 73, 108, 185, 27, 255, 223, 2, 17, 0, 0, 0, 4, 126, 64, 104, 144, 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