Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 995262cbd8d7f332b6a2b81072800c729f3d665de13fbe64ef597ae0a9fdb189

Tx prefix hash: ac896d2168be55f60fb2e0e813f7ad39b7d2e739b62efc089fdafafb711dcf44
Tx public key: 271b0074a7ef49bacf2cdcd4a9f8e0691f49a004a7424507c189f142c71d3ae9
Timestamp: 1644682008 Timestamp [UTC]: 2022-02-12 16:06:48 Age [y:d:h:m:s]: 04:092:15:10:03
Block: 437114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1097087 RingCT/type: yes/0
Extra: 01271b0074a7ef49bacf2cdcd4a9f8e0691f49a004a7424507c189f142c71d3ae9021100000004a272b9cb000000000000000000

1 output(s) for total of 0.021860503521 xmr

stealth address amount amount idx tag
00: 951c7e4d972f31c336397d8094d7d47ecb025f1950dd5528f5706f0de0d65833 0.021860503521 848651 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": 437124, "vin": [ { "gen": { "height": 437114 } } ], "vout": [ { "amount": 21860503521, "target": { "key": "951c7e4d972f31c336397d8094d7d47ecb025f1950dd5528f5706f0de0d65833" } } ], "extra": [ 1, 39, 27, 0, 116, 167, 239, 73, 186, 207, 44, 220, 212, 169, 248, 224, 105, 31, 73, 160, 4, 167, 66, 69, 7, 193, 137, 241, 66, 199, 29, 58, 233, 2, 17, 0, 0, 0, 4, 162, 114, 185, 203, 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: