Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afa1c79dcfe23e1d8d5e6c25a356591c200238d423e611285cab5e2be2ac6459

Tx prefix hash: fe49ff51b18f4f7faf362f379154c688c28df7b38fb245d8caaec7c427bfb0d5
Tx public key: 4962d84a0f4c36de9a0457d59cfcbdb307b79a91062450e969e9fc9b8f1c5243
Timestamp: 1787414364 Timestamp [UTC]: 2026-08-22 15:59:24 Age [y:d:h:m:s]: 00:088:01:42:24
Block: 1619030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 62254 RingCT/type: yes/0
Extra: 014962d84a0f4c36de9a0457d59cfcbdb307b79a91062450e969e9fc9b8f1c52430208679930a15b998ea1

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9445fade58948359d2c69420e2af1bb93cac9b38b6327a7466ac7967d0127d33 0.000600000000 2109050 of 15 <41>

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": 1619040, "vin": [ { "gen": { "height": 1619030 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "9445fade58948359d2c69420e2af1bb93cac9b38b6327a7466ac7967d0127d33", "view_tag": "41" } } } ], "extra": [ 1, 73, 98, 216, 74, 15, 76, 54, 222, 154, 4, 87, 213, 156, 252, 189, 179, 7, 183, 154, 145, 6, 36, 80, 233, 105, 233, 252, 155, 143, 28, 82, 67, 2, 8, 103, 153, 48, 161, 91, 153, 142, 161 ], "rct_signatures": { "type": 0 } }


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