Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4130aea2502db619e3cddb541ab83e9b4e5ffaf65c5b4fd724c4da431c53287e

Tx prefix hash: 76761b87656e8a0e2c441fdbb4223c37e200ade0bf5600ae331c938bde12dc1b
Tx public key: 590601f11adacedda8c025a94e7971e011f8aa56685dbb83ece146369a1fc152
Timestamp: 1772474363 Timestamp [UTC]: 2026-03-02 17:59:23 Age [y:d:h:m:s]: 00:263:19:01:45
Block: 1489229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194189 RingCT/type: yes/0
Extra: 01590601f11adacedda8c025a94e7971e011f8aa56685dbb83ece146369a1fc152021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d62bb74af2a845f8da61d71d295a0a29835100e59bf94d15bf4385d39fa6e6bb 0.000600000000 1978717 of 15 -

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": 1489239, "vin": [ { "gen": { "height": 1489229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d62bb74af2a845f8da61d71d295a0a29835100e59bf94d15bf4385d39fa6e6bb" } } ], "extra": [ 1, 89, 6, 1, 241, 26, 218, 206, 221, 168, 192, 37, 169, 78, 121, 113, 224, 17, 248, 170, 86, 104, 93, 187, 131, 236, 225, 70, 54, 154, 31, 193, 82, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: