Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d24bbf6641bd0fb8a3266d3c4162d0a970803afa19bbc67289add1501f6c1337

Tx prefix hash: fd71196dbd614d36788f8d3ae4696660be9f091fca4d8d537b17f74e2bda846b
Tx public key: 4c86eb6dbcafb59366493ebf7630205fb8d19f8d0b48b496464d515914f1bf70
Timestamp: 1712269734 Timestamp [UCT]: 2024-04-04 22:28:54 Age [y:d:h:m:s]: 00:223:11:30:09
Block: 993450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160003 RingCT/type: yes/0
Extra: 014c86eb6dbcafb59366493ebf7630205fb8d19f8d0b48b496464d515914f1bf700211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45646259f53824007d67e235fa4c54c11bc2db9eb8358c593be6d629682c959c 0.600000000000 1453836 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": 993460, "vin": [ { "gen": { "height": 993450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45646259f53824007d67e235fa4c54c11bc2db9eb8358c593be6d629682c959c" } } ], "extra": [ 1, 76, 134, 235, 109, 188, 175, 181, 147, 102, 73, 62, 191, 118, 48, 32, 95, 184, 209, 159, 141, 11, 72, 180, 150, 70, 77, 81, 89, 20, 241, 191, 112, 2, 17, 0, 0, 0, 4, 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