Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a1eb18b2d1f2d6dd17f179d7923621dcfbc03a6c55c0f22114c0d9c31a8cfb0

Tx prefix hash: 85260ab2d6ca0a48effc5cc0bf341f59c003aa4a4d1f7cb1d04da44e03d5688d
Tx public key: 503a364f05a129fe0408f76986ad16da5a7f9da0767ce847e3840a420e15e7b0
Timestamp: 1604642634 Timestamp [UTC]: 2020-11-06 06:03:54 Age [y:d:h:m:s]: 05:292:06:00:52
Block: 146666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1473261 RingCT/type: yes/0
Extra: 01503a364f05a129fe0408f76986ad16da5a7f9da0767ce847e3840a420e15e7b00211000001362b5659aa000000000000000000

1 output(s) for total of 0.200463520759 xmr

stealth address amount amount idx tag
00: cf2591d45018b366bb66c0128164df139aac335bb0f407b20e423500f3e1aa84 0.200463520759 243610 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": 146676, "vin": [ { "gen": { "height": 146666 } } ], "vout": [ { "amount": 200463520759, "target": { "key": "cf2591d45018b366bb66c0128164df139aac335bb0f407b20e423500f3e1aa84" } } ], "extra": [ 1, 80, 58, 54, 79, 5, 161, 41, 254, 4, 8, 247, 105, 134, 173, 22, 218, 90, 127, 157, 160, 118, 124, 232, 71, 227, 132, 10, 66, 14, 21, 231, 176, 2, 17, 0, 0, 1, 54, 43, 86, 89, 170, 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: