Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b3a86aacce866ea152238e9b35eb879f70a13a3dcdc2ec00bb81f441301b1b6

Tx prefix hash: b116a5e6a8052aa2d76829cf9358b4c97b1f03b45524e04a2102f5c3af84f7c0
Tx public key: 7678d34be8b9c6b2044b45e1201fb242d13dbe3f2011146814c7424a307e2ce2
Timestamp: 1578543017 Timestamp [UTC]: 2020-01-09 04:10:17 Age [y:d:h:m:s]: 06:041:15:37:52
Block: 41758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1438217 RingCT/type: yes/0
Extra: 017678d34be8b9c6b2044b45e1201fb242d13dbe3f2011146814c7424a307e2ce2021100000001391a8d0e000000000000000000

1 output(s) for total of 0.446322381771 xmr

stealth address amount amount idx tag
00: 9d298a6a0f651b8d24ba6c087011dccb9f81caa1c9e3280b5009f20964efcca0 0.446322381771 74730 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": 41768, "vin": [ { "gen": { "height": 41758 } } ], "vout": [ { "amount": 446322381771, "target": { "key": "9d298a6a0f651b8d24ba6c087011dccb9f81caa1c9e3280b5009f20964efcca0" } } ], "extra": [ 1, 118, 120, 211, 75, 232, 185, 198, 178, 4, 75, 69, 225, 32, 31, 178, 66, 209, 61, 190, 63, 32, 17, 20, 104, 20, 199, 66, 74, 48, 126, 44, 226, 2, 17, 0, 0, 0, 1, 57, 26, 141, 14, 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