Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54aa24995e6bbd756a15cca86af69ebf0d827f517f75e6ceef3f8395a575957e

Tx prefix hash: dc6bb4ed774a33e4a5b26fa570e1c4e5c556a1fa21e9cde9a17890656675f578
Tx public key: 0ca51865580ed614d089b56e63865b521f5b43def18df0ff4f61653ff78ec426
Timestamp: 1735007694 Timestamp [UCT]: 2024-12-24 02:34:54 Age [y:d:h:m:s]: 00:106:01:57:16
Block: 1181869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75589 RingCT/type: yes/0
Extra: 010ca51865580ed614d089b56e63865b521f5b43def18df0ff4f61653ff78ec4260211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 947f53335d425d95f4d0ad644af8afe0666d0a24b3b294e7b6a76fa6f249bb30 0.600000000000 1668298 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": 1181879, "vin": [ { "gen": { "height": 1181869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "947f53335d425d95f4d0ad644af8afe0666d0a24b3b294e7b6a76fa6f249bb30" } } ], "extra": [ 1, 12, 165, 24, 101, 88, 14, 214, 20, 208, 137, 181, 110, 99, 134, 91, 82, 31, 91, 67, 222, 241, 141, 240, 255, 79, 97, 101, 63, 247, 142, 196, 38, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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