Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c981b3d5e25c33f849a06b7ae7ce5d0cceba5c69ec6de00233989b41b7d9c5a

Tx prefix hash: 6bf83c3c899eb37b311c6096fedde92877fc4463f6f0560c03d67138980298a0
Tx public key: 507d5dfdc2d15e1d77977a2f8113120aa8e66a9346e6761ae2c13356a13f2c90
Timestamp: 1787372870 Timestamp [UTC]: 2026-08-22 04:27:50 Age [y:d:h:m:s]: 00:092:05:14:12
Block: 1618682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 64812 RingCT/type: yes/0
Extra: 01507d5dfdc2d15e1d77977a2f8113120aa8e66a9346e6761ae2c13356a13f2c90020858f83ce85a7319ed

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 973bdc9be7f86d6ed2b15f8050e1eca1e5066bc3279a1fca1c02290a30faf1b6 0.000600000000 2108702 of 15 <21>

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": 1618692, "vin": [ { "gen": { "height": 1618682 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "973bdc9be7f86d6ed2b15f8050e1eca1e5066bc3279a1fca1c02290a30faf1b6", "view_tag": "21" } } } ], "extra": [ 1, 80, 125, 93, 253, 194, 209, 94, 29, 119, 151, 122, 47, 129, 19, 18, 10, 168, 230, 106, 147, 70, 230, 118, 26, 226, 193, 51, 86, 161, 63, 44, 144, 2, 8, 88, 248, 60, 232, 90, 115, 25, 237 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: