Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90957982d2aa201330f365e1f04ef6c6da816048b175dcac53d29dd0ff7e8f1a

Tx prefix hash: 99a5bfbf6e0757e3cb6ee8c37ace171753c9331ff61ab3e21e85b03c822453f3
Tx public key: 5ab87c85d5a0012bafde0802315e53e98c1a7f5229d3dfcd8621e829eaf5b533
Timestamp: 1574380355 Timestamp [UTC]: 2019-11-21 23:52:35 Age [y:d:h:m:s]: 07:001:13:21:04
Block: 14027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1669401 RingCT/type: yes/0
Extra: 015ab87c85d5a0012bafde0802315e53e98c1a7f5229d3dfcd8621e829eaf5b53302110000000166a80d00000000000000000000

1 output(s) for total of 0.551472183973 xmr

stealth address amount amount idx tag
00: ed44ee63fde14cfefff0d37da94653d7e56b3f1d2e32bc938b07b8c83d9fd42c 0.551472183973 17285 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": 14037, "vin": [ { "gen": { "height": 14027 } } ], "vout": [ { "amount": 551472183973, "target": { "key": "ed44ee63fde14cfefff0d37da94653d7e56b3f1d2e32bc938b07b8c83d9fd42c" } } ], "extra": [ 1, 90, 184, 124, 133, 213, 160, 1, 43, 175, 222, 8, 2, 49, 94, 83, 233, 140, 26, 127, 82, 41, 211, 223, 205, 134, 33, 232, 41, 234, 245, 181, 51, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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: