Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c055eefc6e5ab778b7ef1b871fc876916cbad71d5fa14f2bb9207a480ed4ca6

Tx prefix hash: 58b6a41848f8a8131d5f4a204f5cbe19da7d64427701a10b1bf514e3e0879bb3
Tx public key: 0f6617ecf59d0760d6eb3ffa45c8f2bff97ae4658ba96388fd8f0fa536ff7ede
Timestamp: 1724964468 Timestamp [UCT]: 2024-08-29 20:47:48 Age [y:d:h:m:s]: 00:248:04:05:14
Block: 1098703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177241 RingCT/type: yes/0
Extra: 010f6617ecf59d0760d6eb3ffa45c8f2bff97ae4658ba96388fd8f0fa536ff7ede021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5badc7b69b78896240751d7856cc35531eba0fccd26f98c1abcb01e8e9a19841 0.600000000000 1574514 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": 1098713, "vin": [ { "gen": { "height": 1098703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5badc7b69b78896240751d7856cc35531eba0fccd26f98c1abcb01e8e9a19841" } } ], "extra": [ 1, 15, 102, 23, 236, 245, 157, 7, 96, 214, 235, 63, 250, 69, 200, 242, 191, 249, 122, 228, 101, 139, 169, 99, 136, 253, 143, 15, 165, 54, 255, 126, 222, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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