Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae0c06d55db95417b7509c2351a69fe1ded2d41fe51869f7dfe4e3ecad30bd40

Tx prefix hash: 9a30bd51b0a918a2578d92b15c2fa97d51203cc5099d05a4b127747956b2156b
Tx public key: 03a3546bdf2c27e52a508605cfc7a444e11ef18f3aa4e4df79bbe60a21d12c04
Timestamp: 1706534187 Timestamp [UCT]: 2024-01-29 13:16:27 Age [y:d:h:m:s]: 01:059:13:42:26
Block: 945894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303656 RingCT/type: yes/0
Extra: 0103a3546bdf2c27e52a508605cfc7a444e11ef18f3aa4e4df79bbe60a21d12c0402110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57a33600a66d473b0257f0d3b8421adbb75be1c46948e352b0f43e21d47fe372 0.600000000000 1404218 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": 945904, "vin": [ { "gen": { "height": 945894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57a33600a66d473b0257f0d3b8421adbb75be1c46948e352b0f43e21d47fe372" } } ], "extra": [ 1, 3, 163, 84, 107, 223, 44, 39, 229, 42, 80, 134, 5, 207, 199, 164, 68, 225, 30, 241, 143, 58, 164, 228, 223, 121, 187, 230, 10, 33, 209, 44, 4, 2, 17, 0, 0, 0, 8, 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