Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2059b7a055054abd20efcaa494ee1d18492cdfc71637e9ef02633bf66d1dffd

Tx prefix hash: d87b8cccb57bec464db94c46d8d55416ebe4dda05db7c242e7439223e0415cf5
Tx public key: 038a72ceae4f38c6d81346dc3803e5e3365f90d7d669d6765572751f6b08487e
Timestamp: 1604483003 Timestamp [UTC]: 2020-11-04 09:43:23 Age [y:d:h:m:s]: 06:016:07:33:05
Block: 145924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1536112 RingCT/type: yes/0
Extra: 01038a72ceae4f38c6d81346dc3803e5e3365f90d7d669d6765572751f6b08487e02110000000ba45716b1000000000000000000

1 output(s) for total of 0.201601569458 xmr

stealth address amount amount idx tag
00: f6ee2af33b570f74e65b15cbe5e4c0c8be27aea1e0e99997e4d09b2924b1babb 0.201601569458 242458 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": 145934, "vin": [ { "gen": { "height": 145924 } } ], "vout": [ { "amount": 201601569458, "target": { "key": "f6ee2af33b570f74e65b15cbe5e4c0c8be27aea1e0e99997e4d09b2924b1babb" } } ], "extra": [ 1, 3, 138, 114, 206, 174, 79, 56, 198, 216, 19, 70, 220, 56, 3, 229, 227, 54, 95, 144, 215, 214, 105, 214, 118, 85, 114, 117, 31, 107, 8, 72, 126, 2, 17, 0, 0, 0, 11, 164, 87, 22, 177, 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: