Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b614bd94c5e48df68a9fbdcc9a4a040b05eb0ea2e09c5524dce7b443f5e6551

Tx prefix hash: 4aa3b54d60ae5351e676f039a5ec19c5c0a0441ff39ba14fa2bc972b5ac18174
Tx public key: 7ea9680a7e63e10d38fd92eee60836eae516da641ccd4f1ed69865326357bf0a
Timestamp: 1781625057 Timestamp [UTC]: 2026-06-16 15:50:57 Age [y:d:h:m:s]: 00:156:02:54:25
Block: 1560844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 121236 RingCT/type: yes/0
Extra: 017ea9680a7e63e10d38fd92eee60836eae516da641ccd4f1ed69865326357bf0a

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a80ea631fa5842760974555269fe08e780783ef58a5e666f8ecf0854309f5ea6 0.000600000000 2050822 of 15 <66>

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": 1560854, "vin": [ { "gen": { "height": 1560844 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "a80ea631fa5842760974555269fe08e780783ef58a5e666f8ecf0854309f5ea6", "view_tag": "66" } } } ], "extra": [ 1, 126, 169, 104, 10, 126, 99, 225, 13, 56, 253, 146, 238, 230, 8, 54, 234, 229, 22, 218, 100, 28, 205, 79, 30, 214, 152, 101, 50, 99, 87, 191, 10 ], "rct_signatures": { "type": 0 } }


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