Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d84787ccdda9b1d80a9fb271e11aa7dd8881c286c855f78df429ba0331b4153

Tx prefix hash: 9f1609c1d4efb574c1527c7d772da83ee043657e56d37e6ab370b8938ae431d4
Tx public key: c4d8a1de7c477ae67f606a878dd0cf732fccc5bd199001f0d05c82df79be323f
Timestamp: 1728319940 Timestamp [UCT]: 2024-10-07 16:52:20 Age [y:d:h:m:s]: 00:048:06:27:10
Block: 1126528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34484 RingCT/type: yes/0
Extra: 01c4d8a1de7c477ae67f606a878dd0cf732fccc5bd199001f0d05c82df79be323f021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1c72e8889d9e8dba039950b9239b95cfc8e81705fd554ca16a6489d8799ec1f 0.600000000000 1609323 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": 1126538, "vin": [ { "gen": { "height": 1126528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1c72e8889d9e8dba039950b9239b95cfc8e81705fd554ca16a6489d8799ec1f" } } ], "extra": [ 1, 196, 216, 161, 222, 124, 71, 122, 230, 127, 96, 106, 135, 141, 208, 207, 115, 47, 204, 197, 189, 25, 144, 1, 240, 208, 92, 130, 223, 121, 190, 50, 63, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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