Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d26904c7a577d7e1351cd929c4d1a13e22c8b76c4e67febf217ded636356643

Tx prefix hash: 342825f413efe70f2545da6c9bbe93276998a2420f317b7b7314424493e168cc
Tx public key: f1ae8accd2b19a2086a1313b7423e5f4026b9ced571046a71278d46c54ccf8f7
Timestamp: 1781933121 Timestamp [UTC]: 2026-06-20 05:25:21 Age [y:d:h:m:s]: 00:155:05:00:36
Block: 1563592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 119902 RingCT/type: yes/0
Extra: 01f1ae8accd2b19a2086a1313b7423e5f4026b9ced571046a71278d46c54ccf8f70208725ec977f2100ea4

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d10e3534b1f95d6baab20d5aa132527e720b59289d0f7d3441899fbe9ef1d1b1 0.000600000000 2053570 of 15 <c4>

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": 1563602, "vin": [ { "gen": { "height": 1563592 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "d10e3534b1f95d6baab20d5aa132527e720b59289d0f7d3441899fbe9ef1d1b1", "view_tag": "c4" } } } ], "extra": [ 1, 241, 174, 138, 204, 210, 177, 154, 32, 134, 161, 49, 59, 116, 35, 229, 244, 2, 107, 156, 237, 87, 16, 70, 167, 18, 120, 212, 108, 84, 204, 248, 247, 2, 8, 114, 94, 201, 119, 242, 16, 14, 164 ], "rct_signatures": { "type": 0 } }


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