Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d43f03c682bf2d07d4a00f5373f8ba60d6751ea8a6a5c079665c5db641a6cea1

Tx prefix hash: df05a6a1a83f0bb8a310d5d4c9c7246c31737020bf53da144456bd6d29aef1cd
Tx public key: 41bf67689875c769ad1af73217c722c3f911dd70c70164fa4a35c46801b1ad34
Timestamp: 1700438703 Timestamp [UTC]: 2023-11-20 00:05:03 Age [y:d:h:m:s]: 02:178:05:14:33
Block: 895383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 639516 RingCT/type: yes/0
Extra: 0141bf67689875c769ad1af73217c722c3f911dd70c70164fa4a35c46801b1ad3402110000000575e3f0e9000000000000000000

1 output(s) for total of 0.000662558790 xmr

stealth address amount amount idx tag
00: 86623440267f5a9e318dedf36bc707a3895339a7023e9a77cbcbf929374425bd 0.000662558790 1351616 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": 895393, "vin": [ { "gen": { "height": 895383 } } ], "vout": [ { "amount": 662558790, "target": { "key": "86623440267f5a9e318dedf36bc707a3895339a7023e9a77cbcbf929374425bd" } } ], "extra": [ 1, 65, 191, 103, 104, 152, 117, 199, 105, 173, 26, 247, 50, 23, 199, 34, 195, 249, 17, 221, 112, 199, 1, 100, 250, 74, 53, 196, 104, 1, 177, 173, 52, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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: