Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2abb018196e6bf2ec5fe7deabc19c136e74147bd3b3323d683566b0635480cf3

Tx prefix hash: 09bcdda243ab70757fcdc7df467c94b75a584ce7a58f9bf30c92a731c14d719d
Tx public key: 2297ea8d2945074349eae10740216a68b00a0bc33c4d046c2a5ac1018ce14349
Timestamp: 1744354002 Timestamp [UTC]: 2025-04-11 06:46:42 Age [y:d:h:m:s]: 00:311:22:46:10
Block: 1258967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220587 RingCT/type: yes/0
Extra: 012297ea8d2945074349eae10740216a68b00a0bc33c4d046c2a5ac1018ce14349021100000002a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2f03440fd1534746f8959ccab5dcb18661dec2faf7f6dde0ba7ea4a1e5c031cc 0.000600000000 1746104 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": 1258977, "vin": [ { "gen": { "height": 1258967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f03440fd1534746f8959ccab5dcb18661dec2faf7f6dde0ba7ea4a1e5c031cc" } } ], "extra": [ 1, 34, 151, 234, 141, 41, 69, 7, 67, 73, 234, 225, 7, 64, 33, 106, 104, 176, 10, 11, 195, 60, 77, 4, 108, 42, 90, 193, 1, 140, 225, 67, 73, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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) | dinastycoin version: tesla-369