Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3299e783bd4a3b289851f3c36f68b428e192075cb25c7458ca8886df5797e37f

Tx prefix hash: 2ad1d74976a106ec8a9659ba1da828b9e1a051d0d0bd56d4fbf1fe38ed9c5fb2
Tx public key: b12cd87fc3b0ce9270b5a26d9946ef22062d52516b125b161d98184c447ef026
Timestamp: 1695614743 Timestamp [UCT]: 2023-09-25 04:05:43 Age [y:d:h:m:s]: 02:041:02:09:59
Block: 855586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549017 RingCT/type: yes/0
Extra: 01b12cd87fc3b0ce9270b5a26d9946ef22062d52516b125b161d98184c447ef026021100000002faf35c9c000000000000000000

1 output(s) for total of 0.897611607000 dcy

stealth address amount amount idx
00: 1f523da17ae176ea198fd4da3f36bf7471f6c6da478dbf29315ab8171ff862ff 0.897611607000 1309614 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 dinasty-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": 855596, "vin": [ { "gen": { "height": 855586 } } ], "vout": [ { "amount": 897611607, "target": { "key": "1f523da17ae176ea198fd4da3f36bf7471f6c6da478dbf29315ab8171ff862ff" } } ], "extra": [ 1, 177, 44, 216, 127, 195, 176, 206, 146, 112, 181, 162, 109, 153, 70, 239, 34, 6, 45, 82, 81, 107, 18, 91, 22, 29, 152, 24, 76, 68, 126, 240, 38, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8