Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bda376efa102533410541287c589877740f780f8692e4ca42ac49537d19024ef

Tx prefix hash: 11767bb6559774d452390422f2457bb95e9e20ff638bc2feb90a0c9141f08123
Tx public key: 6a840c3273cd1929d2a5c8f81c7faba8d327b41bbe5ddc59694c9c2b4e4c022b
Timestamp: 1577704947 Timestamp [UTC]: 2019-12-30 11:22:27 Age [y:d:h:m:s]: 06:270:08:37:40
Block: 34980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1607793 RingCT/type: yes/0
Extra: 016a840c3273cd1929d2a5c8f81c7faba8d327b41bbe5ddc59694c9c2b4e4c022b02110000001d8a2ee0d9000000000000000000

1 output(s) for total of 0.470007824473 xmr

stealth address amount amount idx tag
00: d40127991ef080499715fb9433a190b2b42b360d0b5f279c6c04b6e99bd15326 0.470007824473 58933 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": 34990, "vin": [ { "gen": { "height": 34980 } } ], "vout": [ { "amount": 470007824473, "target": { "key": "d40127991ef080499715fb9433a190b2b42b360d0b5f279c6c04b6e99bd15326" } } ], "extra": [ 1, 106, 132, 12, 50, 115, 205, 25, 41, 210, 165, 200, 248, 28, 127, 171, 168, 211, 39, 180, 27, 190, 93, 220, 89, 105, 76, 156, 43, 78, 76, 2, 43, 2, 17, 0, 0, 0, 29, 138, 46, 224, 217, 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) | monero version: