Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc710420fd0cbfd5b3a21a1423f07dcf1bf2bf922a8c56637c5b5b0e65ee1caf

Tx prefix hash: d25b6c3c1dc5f358e6afc32ea72f9a293e1561848570f7ecb02d2b2d1ec39b96
Tx public key: 018ba5952c2f8efa9836d976f829a9cfe21d91e6b39456feba0abdfd0b47f44e
Timestamp: 1734564386 Timestamp [UCT]: 2024-12-18 23:26:26 Age [y:d:h:m:s]: 00:108:17:00:20
Block: 1178213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77452 RingCT/type: yes/0
Extra: 01018ba5952c2f8efa9836d976f829a9cfe21d91e6b39456feba0abdfd0b47f44e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5adaf879435ef3d126bf52b9c6b05a72870714f76de306004e0fc83b48d89e32 0.600000000000 1664598 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": 1178223, "vin": [ { "gen": { "height": 1178213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5adaf879435ef3d126bf52b9c6b05a72870714f76de306004e0fc83b48d89e32" } } ], "extra": [ 1, 1, 139, 165, 149, 44, 47, 142, 250, 152, 54, 217, 118, 248, 41, 169, 207, 226, 29, 145, 230, 179, 148, 86, 254, 186, 10, 189, 253, 11, 71, 244, 78, 2, 17, 0, 0, 0, 1, 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