Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d0bf2a8c1c07f437a0e5d3f206d4a90a980bd6f706a4d4e17d4878e349a440b

Tx prefix hash: 1b94898934ebeb3ceecdcf9d57071a3a54151d3963f37ea1b58b7de1c774da6d
Tx public key: ec535b6f468db61de54dd5b9ab2b34ce3c5ff901455ccf31b109335e01e88c1f
Timestamp: 1579116556 Timestamp [UTC]: 2020-01-15 19:29:16 Age [y:d:h:m:s]: 06:309:20:10:26
Block: 46237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1635747 RingCT/type: yes/0
Extra: 01ec535b6f468db61de54dd5b9ab2b34ce3c5ff901455ccf31b109335e01e88c1f0211000000ac17786bcf000000000000000000

1 output(s) for total of 0.431357264827 xmr

stealth address amount amount idx tag
00: 5446e03bdabea7281db999fc814ab9f205e595ef197bbd90405d9e756442881e 0.431357264827 84949 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": 46247, "vin": [ { "gen": { "height": 46237 } } ], "vout": [ { "amount": 431357264827, "target": { "key": "5446e03bdabea7281db999fc814ab9f205e595ef197bbd90405d9e756442881e" } } ], "extra": [ 1, 236, 83, 91, 111, 70, 141, 182, 29, 229, 77, 213, 185, 171, 43, 52, 206, 60, 95, 249, 1, 69, 92, 207, 49, 177, 9, 51, 94, 1, 232, 140, 31, 2, 17, 0, 0, 0, 172, 23, 120, 107, 207, 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: