Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6159cc534a5253adebcce3e9c732c342fafbf84d9b2671835e72610ea922cd40

Tx prefix hash: 8ae5e3c6d18dbd2c785a25c9e0281389b6decfbd681e44ff53143468ed54e3f7
Tx public key: e0cb570f4349071fe5571dc696e7d6cacf075685615de151c3664af082f4b19b
Timestamp: 1578077774 Timestamp [UTC]: 2020-01-03 18:56:14 Age [y:d:h:m:s]: 06:137:07:02:16
Block: 37917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1499395 RingCT/type: yes/0
Extra: 01e0cb570f4349071fe5571dc696e7d6cacf075685615de151c3664af082f4b19b02110000000b8a2ee0d9000000000000000000

1 output(s) for total of 0.459585258111 xmr

stealth address amount amount idx tag
00: f45dd8507464eb8f63721958e1701725506972ccae8ef514331e21192f39c0bc 0.459585258111 64474 of 0 -

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 dinastycoin-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": 37927, "vin": [ { "gen": { "height": 37917 } } ], "vout": [ { "amount": 459585258111, "target": { "key": "f45dd8507464eb8f63721958e1701725506972ccae8ef514331e21192f39c0bc" } } ], "extra": [ 1, 224, 203, 87, 15, 67, 73, 7, 31, 229, 87, 29, 198, 150, 231, 214, 202, 207, 7, 86, 133, 97, 93, 225, 81, 195, 102, 74, 240, 130, 244, 177, 155, 2, 17, 0, 0, 0, 11, 138, 46, 224, 217, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: