Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55bad4f650159bbaf0e79c746a1d355c6007e50774a1aedd5b43d246c93696f0

Tx prefix hash: 919a602a22a2de6560d4efbd8aa483b9e9493faef777c17b26561a6c68f3c5b8
Tx public key: fe5a6054e70ffdea509b2b2c27821a5dd4347b925d82fb8ed80864aa86448a73
Timestamp: 1578055272 Timestamp [UTC]: 2020-01-03 12:41:12 Age [y:d:h:m:s]: 06:264:23:02:21
Block: 37719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1604066 RingCT/type: yes/0
Extra: 01fe5a6054e70ffdea509b2b2c27821a5dd4347b925d82fb8ed80864aa86448a73021100000004d81c26c0000000000000000000

1 output(s) for total of 0.460321914144 xmr

stealth address amount amount idx tag
00: f93059a6a4162011986b176ea96ba49f1f25f077f7cb4b156f5733e076eeb9f5 0.460321914144 64126 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": 37729, "vin": [ { "gen": { "height": 37719 } } ], "vout": [ { "amount": 460321914144, "target": { "key": "f93059a6a4162011986b176ea96ba49f1f25f077f7cb4b156f5733e076eeb9f5" } } ], "extra": [ 1, 254, 90, 96, 84, 231, 15, 253, 234, 80, 155, 43, 44, 39, 130, 26, 93, 212, 52, 123, 146, 93, 130, 251, 142, 216, 8, 100, 170, 134, 68, 138, 115, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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: