Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe5b6a9ed3d2964c909c8b7ff061de05f5fed5701659482d2fd204e11e04b874

Tx prefix hash: 6ab29d635fa8f28aa51525475753a57f5c5a20cfdb67e6193a7fdfd2ca7a0ace
Tx public key: 864a2dcb7434d3f601f72ead1f15115a7b027678ec21fb9874cf0882e3ef9a84
Timestamp: 1580476948 Timestamp [UTC]: 2020-01-31 13:22:28 Age [y:d:h:m:s]: 06:106:10:13:27
Block: 55740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1478980 RingCT/type: yes/0
Extra: 01864a2dcb7434d3f601f72ead1f15115a7b027678ec21fb9874cf0882e3ef9a84021100000002b221b3d1000000000000000000

1 output(s) for total of 0.401153943457 xmr

stealth address amount amount idx tag
00: a26f21e1c05f0f3148574ecaf2b5027872bc05a8acfb261fe8417aefb725e884 0.401153943457 102853 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": 55750, "vin": [ { "gen": { "height": 55740 } } ], "vout": [ { "amount": 401153943457, "target": { "key": "a26f21e1c05f0f3148574ecaf2b5027872bc05a8acfb261fe8417aefb725e884" } } ], "extra": [ 1, 134, 74, 45, 203, 116, 52, 211, 246, 1, 247, 46, 173, 31, 21, 17, 90, 123, 2, 118, 120, 236, 33, 251, 152, 116, 207, 8, 130, 227, 239, 154, 132, 2, 17, 0, 0, 0, 2, 178, 33, 179, 209, 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: