Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f3cffd7dcfb4c02b7fabb0f851d0f8f37aad4969021ba55b3a4e2f0e8f66409

Tx prefix hash: 1f0348fb83bf7dd31af59dfcdab67777563e2fabdd1681c88e6ccc45fc2c75fe
Tx public key: 7fa7695fad37172bf0d916e9c41cf80120cfd327ce18345c56243f6a3e5f2b25
Timestamp: 1656329955 Timestamp [UTC]: 2022-06-27 11:39:15 Age [y:d:h:m:s]: 03:243:20:58:54
Block: 531445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 953961 RingCT/type: yes/0
Extra: 017fa7695fad37172bf0d916e9c41cf80120cfd327ce18345c56243f6a3e5f2b25021100000001cb8520c2000000000000000000

1 output(s) for total of 0.010643936161 xmr

stealth address amount amount idx tag
00: 475733060a352acba3a772a21b2d0628dbf3b23b69b16a622a58d4e3573c9851 0.010643936161 960592 of 0 -

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": 531455, "vin": [ { "gen": { "height": 531445 } } ], "vout": [ { "amount": 10643936161, "target": { "key": "475733060a352acba3a772a21b2d0628dbf3b23b69b16a622a58d4e3573c9851" } } ], "extra": [ 1, 127, 167, 105, 95, 173, 55, 23, 43, 240, 217, 22, 233, 196, 28, 248, 1, 32, 207, 211, 39, 206, 24, 52, 92, 86, 36, 63, 106, 62, 95, 43, 37, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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