Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a505e1fd0cc04075fcccc60ca0d6c7abd1288ae6f19d24322d8ab0174e1fa17

Tx prefix hash: 631edb814c5b50db955cb74a2d5d724b61876c67d1aa8a70e6bd6ccc1ad69fa2
Tx public key: 780a704cfe00a1e6ae8da9bf24c7948f3534440b92de990a2dcd544421e97fde
Timestamp: 1746974351 Timestamp [UTC]: 2025-05-11 14:39:11 Age [y:d:h:m:s]: 01:194:13:11:43
Block: 1280658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402836 RingCT/type: yes/0
Extra: 01780a704cfe00a1e6ae8da9bf24c7948f3534440b92de990a2dcd544421e97fde02110000000601491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c2f133171a8c4be5f691f5a10509ef9df5ae1c5c768eb61764534c29c2db26bb 0.000600000000 1768047 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": 1280668, "vin": [ { "gen": { "height": 1280658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2f133171a8c4be5f691f5a10509ef9df5ae1c5c768eb61764534c29c2db26bb" } } ], "extra": [ 1, 120, 10, 112, 76, 254, 0, 161, 230, 174, 141, 169, 191, 36, 199, 148, 143, 53, 52, 68, 11, 146, 222, 153, 10, 45, 205, 84, 68, 33, 233, 127, 222, 2, 17, 0, 0, 0, 6, 1, 73, 31, 136, 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: