Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3049ad31cbed193b16826d0e1ed829a0f59bf9721fe28af9dda2ead8a93a566

Tx prefix hash: d91af1f8d1407cdbc47391e19da98b03f740477cdb37734bf980e3a9bd42c859
Tx public key: 11a55176a6b4b8b9a626852f1f40c58d09ae05d89360f0183225217a065751c3
Timestamp: 1617512951 Timestamp [UTC]: 2021-04-04 05:09:11 Age [y:d:h:m:s]: 05:233:06:23:11
Block: 232878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1450616 RingCT/type: yes/0
Extra: 0111a55176a6b4b8b9a626852f1f40c58d09ae05d89360f0183225217a065751c30211000000173a645b90000000000000000000

1 output(s) for total of 0.103843445894 xmr

stealth address amount amount idx tag
00: d2cc0034e87b9a9be25b7a2cd460bd385e4a529f7c6ee6dc164ecdf00264fd94 0.103843445894 483738 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": 232888, "vin": [ { "gen": { "height": 232878 } } ], "vout": [ { "amount": 103843445894, "target": { "key": "d2cc0034e87b9a9be25b7a2cd460bd385e4a529f7c6ee6dc164ecdf00264fd94" } } ], "extra": [ 1, 17, 165, 81, 118, 166, 180, 184, 185, 166, 38, 133, 47, 31, 64, 197, 141, 9, 174, 5, 216, 147, 96, 240, 24, 50, 37, 33, 122, 6, 87, 81, 195, 2, 17, 0, 0, 0, 23, 58, 100, 91, 144, 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: