Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e70ba69e64a39beedb95babe905d057ac2bab130a82ea8954ce7bffb438f0600

Tx prefix hash: 066c040f500aa8f8978dca258579b9c71b0903e4b65111d2d15f5f6b2a947f18
Tx public key: 8504703dece7e93bef1e6248b723716f84b954f407eca629c295ba1a9aa45128
Timestamp: 1580473241 Timestamp [UTC]: 2020-01-31 12:20:41 Age [y:d:h:m:s]: 06:109:15:44:56
Block: 55663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1482027 RingCT/type: yes/0
Extra: 018504703dece7e93bef1e6248b723716f84b954f407eca629c295ba1a9aa4512802110000000817786bcf000000000000000000

1 output(s) for total of 0.401396606843 xmr

stealth address amount amount idx tag
00: 7f911914e99dddb425cbc4854e12fa87bd7c1e7ee3cdb8a72b44ea52fbd30e8b 0.401396606843 102717 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": 55673, "vin": [ { "gen": { "height": 55663 } } ], "vout": [ { "amount": 401396606843, "target": { "key": "7f911914e99dddb425cbc4854e12fa87bd7c1e7ee3cdb8a72b44ea52fbd30e8b" } } ], "extra": [ 1, 133, 4, 112, 61, 236, 231, 233, 59, 239, 30, 98, 72, 183, 35, 113, 111, 132, 185, 84, 244, 7, 236, 166, 41, 194, 149, 186, 26, 154, 164, 81, 40, 2, 17, 0, 0, 0, 8, 23, 120, 107, 207, 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: