Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf4007335e02014c1535ff6f6397679bd940c3b3ed9ccfa8ea2c8c579f73419f

Tx prefix hash: 729f30bb4239370d5bd977236c3acdf9a3b4f9126fcc625439291f5a618e85d7
Tx public key: ec232a852537d24b48cb9a1853fe0fa2c534071ccbff18748b743f45df473ca9
Timestamp: 1713919739 Timestamp [UCT]: 2024-04-24 00:48:59 Age [y:d:h:m:s]: 00:261:12:16:08
Block: 1007140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187189 RingCT/type: yes/0
Extra: 01ec232a852537d24b48cb9a1853fe0fa2c534071ccbff18748b743f45df473ca90211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efac96a1dc1707f5207310c248f5e6ce3c2bb397a5b19b6c76c152647a0482c8 0.600000000000 1468386 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": 1007150, "vin": [ { "gen": { "height": 1007140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efac96a1dc1707f5207310c248f5e6ce3c2bb397a5b19b6c76c152647a0482c8" } } ], "extra": [ 1, 236, 35, 42, 133, 37, 55, 210, 75, 72, 203, 154, 24, 83, 254, 15, 162, 197, 52, 7, 28, 203, 255, 24, 116, 139, 116, 63, 69, 223, 71, 60, 169, 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