Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eee65563c13256125870b518b554aa1d6e285d9cc3a40d23e6fc0925a725428

Tx prefix hash: 4f123897ac0c9cdac9d8cbacec0d4a584288a41c840d1f0eb51a9b9b34992240
Tx public key: 14caf1fa401a043248c1bda32135fd5d13ef09af0925345dc0d39d02a12ab4e7
Timestamp: 1712906401 Timestamp [UCT]: 2024-04-12 07:20:01 Age [y:d:h:m:s]: 01:065:01:10:23
Block: 998727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307388 RingCT/type: yes/0
Extra: 0114caf1fa401a043248c1bda32135fd5d13ef09af0925345dc0d39d02a12ab4e702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91a4f89cc19c78754aea7a4b6daab1fbf58e65684f062ff2075e467de5b9cf45 0.600000000000 1459179 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": 998737, "vin": [ { "gen": { "height": 998727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91a4f89cc19c78754aea7a4b6daab1fbf58e65684f062ff2075e467de5b9cf45" } } ], "extra": [ 1, 20, 202, 241, 250, 64, 26, 4, 50, 72, 193, 189, 163, 33, 53, 253, 93, 19, 239, 9, 175, 9, 37, 52, 93, 192, 211, 157, 2, 161, 42, 180, 231, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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