Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec89c73c8e0431f8d3b42db53ee26c916946fa818d1268f4c8de6c63b422babf

Tx prefix hash: d80a1bc05d2e41560ad6506d987759a415af5f9ba9cbd214d62b3df8e48f1e41
Tx public key: 2d1df311be9d6bfca4dc240fe5e76c63ff5ffd2a9f91e327a269b6e495476816
Timestamp: 1673496792 Timestamp [UCT]: 2023-01-12 04:13:12 Age [y:d:h:m:s]: 02:301:16:54:03
Block: 672875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 735030 RingCT/type: yes/0
Extra: 012d1df311be9d6bfca4dc240fe5e76c63ff5ffd2a9f91e327a269b6e4954768160211000000018b7b6602000000000000000000

1 output(s) for total of 3.618143223000 dcy

stealth address amount amount idx
00: 1ea427e96007981f855c27278b8111de361ae42de878157d5c0faddfa90170bc 3.618143223000 1114444 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": 672885, "vin": [ { "gen": { "height": 672875 } } ], "vout": [ { "amount": 3618143223, "target": { "key": "1ea427e96007981f855c27278b8111de361ae42de878157d5c0faddfa90170bc" } } ], "extra": [ 1, 45, 29, 243, 17, 190, 157, 107, 252, 164, 220, 36, 15, 229, 231, 108, 99, 255, 95, 253, 42, 159, 145, 227, 39, 162, 105, 182, 228, 149, 71, 104, 22, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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