Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1a1dabf97699cb85df5b2cf92253c4d27317b4de85a1ec35c1bc6224ae812d3

Tx prefix hash: 6c91e24248fd811a17b68e805b2869defd9408e7ac4f853d98c98d88749a2b37
Tx public key: 39fb467240147b61e89b1d9bcb9f81387bf533bc77e567955d41dec9ccf045f7
Timestamp: 1735845181 Timestamp [UCT]: 2025-01-02 19:13:01 Age [y:d:h:m:s]: 00:323:08:43:13
Block: 1188786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228625 RingCT/type: yes/0
Extra: 0139fb467240147b61e89b1d9bcb9f81387bf533bc77e567955d41dec9ccf045f7021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b57c4c2e70f083bfac645412b66666cd8ced08b1f0e53be8769dca989683e72f 0.600000000000 1675289 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": 1188796, "vin": [ { "gen": { "height": 1188786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b57c4c2e70f083bfac645412b66666cd8ced08b1f0e53be8769dca989683e72f" } } ], "extra": [ 1, 57, 251, 70, 114, 64, 20, 123, 97, 232, 155, 29, 155, 203, 159, 129, 56, 123, 245, 51, 188, 119, 229, 103, 149, 93, 65, 222, 201, 204, 240, 69, 247, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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