Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed199940e20d6af3755ad75df74c00c03534305dc46128311227769481ad918a

Tx prefix hash: 53927e73d8acec0772eb9ab7bb78302fd8c8a77d21135af9f17b8c10cbf2e020
Tx public key: 743746d273351b52b29e45d9375eba32f91cecc29358482a8128727e5f964d01
Timestamp: 1686421512 Timestamp [UTC]: 2023-06-10 18:25:12 Age [y:d:h:m:s]: 02:239:04:32:06
Block: 779435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 690664 RingCT/type: yes/0
Extra: 01743746d273351b52b29e45d9375eba32f91cecc29358482a8128727e5f964d010211000000034b8f5122000000000000000000

1 output(s) for total of 0.001604753923 xmr

stealth address amount amount idx tag
00: a120f419027094976335fc4e7eda86a9811d01764e46ad6dea4e6dfdbead07d0 0.001604753923 1229090 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": 779445, "vin": [ { "gen": { "height": 779435 } } ], "vout": [ { "amount": 1604753923, "target": { "key": "a120f419027094976335fc4e7eda86a9811d01764e46ad6dea4e6dfdbead07d0" } } ], "extra": [ 1, 116, 55, 70, 210, 115, 53, 27, 82, 178, 158, 69, 217, 55, 94, 186, 50, 249, 28, 236, 194, 147, 88, 72, 42, 129, 40, 114, 126, 95, 150, 77, 1, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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