Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f003d735b1b56146e46efc5edd1bd568a7d710b2c13c32813c04ec53fd3ef176

Tx prefix hash: f12fcdc92eca728ef67b8303b6d93125ae94698a494c0ca2bcfbcc9c67f0c5c3
Tx public key: 28bcabd70e37799e61d044b891546b486ed470c939546c31cb86109021adf72f
Timestamp: 1673387175 Timestamp [UCT]: 2023-01-10 21:46:15 Age [y:d:h:m:s]: 02:090:17:11:21
Block: 671971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 586519 RingCT/type: yes/0
Extra: 0128bcabd70e37799e61d044b891546b486ed470c939546c31cb86109021adf72f021100000003b3e1cbca000000000000000000

1 output(s) for total of 3.643183807000 dcy

stealth address amount amount idx
00: 670c512a2a64f2825926767458813cc220907b594a3d8c562a5ef1a52b9e1eae 3.643183807000 1113482 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": 671981, "vin": [ { "gen": { "height": 671971 } } ], "vout": [ { "amount": 3643183807, "target": { "key": "670c512a2a64f2825926767458813cc220907b594a3d8c562a5ef1a52b9e1eae" } } ], "extra": [ 1, 40, 188, 171, 215, 14, 55, 121, 158, 97, 208, 68, 184, 145, 84, 107, 72, 110, 212, 112, 201, 57, 84, 108, 49, 203, 134, 16, 144, 33, 173, 247, 47, 2, 17, 0, 0, 0, 3, 179, 225, 203, 202, 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