Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afd3b74b34d21c630cb1f343a4bcda1736dac382fa663809d926e227dcf23e8d

Tx prefix hash: 3271be1f9cac6422fdd345d260d7500e712525d012575eb3d0b89d672c4fa427
Tx public key: 7f1b410fa8bd50839c014b2149dff7efd2102594012a82a46ff4d38315228fee
Timestamp: 1671349168 Timestamp [UCT]: 2022-12-18 07:39:28 Age [y:d:h:m:s]: 02:069:23:53:32
Block: 655103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 571676 RingCT/type: yes/0
Extra: 017f1b410fa8bd50839c014b2149dff7efd2102594012a82a46ff4d38315228fee0211000000037e406890000000000000000000

1 output(s) for total of 4.143542463000 dcy

stealth address amount amount idx
00: e6835d2ef9ddf2a073ad80c054efa5a8a50b61ba89c196fc652d6d4bc9eb9365 4.143542463000 1095648 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": 655113, "vin": [ { "gen": { "height": 655103 } } ], "vout": [ { "amount": 4143542463, "target": { "key": "e6835d2ef9ddf2a073ad80c054efa5a8a50b61ba89c196fc652d6d4bc9eb9365" } } ], "extra": [ 1, 127, 27, 65, 15, 168, 189, 80, 131, 156, 1, 75, 33, 73, 223, 247, 239, 210, 16, 37, 148, 1, 42, 130, 164, 111, 244, 211, 131, 21, 34, 143, 238, 2, 17, 0, 0, 0, 3, 126, 64, 104, 144, 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