Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bf0764d5a52175cf6dee85a4c8244c0ef9ec409d32f6073f9789ac53b99f914

Tx prefix hash: 15295a47ba537a53f7ca6fb916cc1e371b6738b1b225102f6ffdc77307ee0cd4
Tx public key: a209c59bcaf05e6175cbb0353b2a171e68f1490669dc4ab020ec562236246e3f
Timestamp: 1577055996 Timestamp [UTC]: 2019-12-22 23:06:36 Age [y:d:h:m:s]: 06:058:15:13:17
Block: 29769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1450048 RingCT/type: yes/0
Extra: 01a209c59bcaf05e6175cbb0353b2a171e68f1490669dc4ab020ec562236246e3f0211000000124ac5aa02000000000000000000

1 output(s) for total of 0.489061874291 xmr

stealth address amount amount idx tag
00: 9e0b5c8c6e94290b19e23c74d7e8423439d0d147c37e74b1182fbfe1008ac8e5 0.489061874291 49049 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": 29779, "vin": [ { "gen": { "height": 29769 } } ], "vout": [ { "amount": 489061874291, "target": { "key": "9e0b5c8c6e94290b19e23c74d7e8423439d0d147c37e74b1182fbfe1008ac8e5" } } ], "extra": [ 1, 162, 9, 197, 155, 202, 240, 94, 97, 117, 203, 176, 53, 59, 42, 23, 30, 104, 241, 73, 6, 105, 220, 74, 176, 32, 236, 86, 34, 54, 36, 110, 63, 2, 17, 0, 0, 0, 18, 74, 197, 170, 2, 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