Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ab90d9c065cbd6726ba8edd24d1d3d6e61e6b4864ff15677c643b993872d09c

Tx prefix hash: 707a87a028494a2e6ff5424cfd5ce8db67e947bc18fadbfb219fe31e02784f18
Tx public key: 58dde1c77bd6cf3fd0c34f0d5d73f28019671234c869f093c2e40823800de11f
Timestamp: 1736690116 Timestamp [UCT]: 2025-01-12 13:55:16 Age [y:d:h:m:s]: 00:075:07:47:57
Block: 1195782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53607 RingCT/type: yes/0
Extra: 0158dde1c77bd6cf3fd0c34f0d5d73f28019671234c869f093c2e40823800de11f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9d4a2829d3fa80898cc4fd5477f3436aea7d0e7ea29ab6e936f968ec3131505 0.600000000000 1682375 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": 1195792, "vin": [ { "gen": { "height": 1195782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9d4a2829d3fa80898cc4fd5477f3436aea7d0e7ea29ab6e936f968ec3131505" } } ], "extra": [ 1, 88, 221, 225, 199, 123, 214, 207, 63, 208, 195, 79, 13, 93, 115, 242, 128, 25, 103, 18, 52, 200, 105, 240, 147, 194, 228, 8, 35, 128, 13, 225, 31, 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