Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c31c583381bf7541d67d5d5f5851155cc2cb1dce842a66f1ae21b78fe6a8a2aa

Tx prefix hash: 155f3b1449443e1f32b684aad12d9e87dfd1e1132f7918a7275254f8d524ead3
Tx public key: aab1329be96fda9856ba2b15a36e6875fc448ce5d9a4ba0abccf43058afe694a
Timestamp: 1649753121 Timestamp [UTC]: 2022-04-12 08:45:21 Age [y:d:h:m:s]: 04:029:21:41:39
Block: 478495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1053034 RingCT/type: yes/0
Extra: 01aab1329be96fda9856ba2b15a36e6875fc448ce5d9a4ba0abccf43058afe694a0211000000012e6b1fd5000000000000000000

1 output(s) for total of 0.015942178566 xmr

stealth address amount amount idx tag
00: 541f7669757bff7ebc9e72a18a9a33fd5e25aa7c2c493e30de9effd2711a8920 0.015942178566 899264 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": 478505, "vin": [ { "gen": { "height": 478495 } } ], "vout": [ { "amount": 15942178566, "target": { "key": "541f7669757bff7ebc9e72a18a9a33fd5e25aa7c2c493e30de9effd2711a8920" } } ], "extra": [ 1, 170, 177, 50, 155, 233, 111, 218, 152, 86, 186, 43, 21, 163, 110, 104, 117, 252, 68, 140, 229, 217, 164, 186, 10, 188, 207, 67, 5, 138, 254, 105, 74, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 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: