Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c33df4e84e55247eb15f107b7a54a44af9dee96bf51185142b27045d75a05b1c

Tx prefix hash: 74af12ec8f70638b1972d975cb1744e6ba0462ae95f53c962ec64838bd4f52ce
Tx public key: fbedbae654ad5f1d8a636a648df87bdc6f9ef84d7e8283b37c151ae4000f75eb
Timestamp: 1679496729 Timestamp [UCT]: 2023-03-22 14:52:09 Age [y:d:h:m:s]: 02:040:00:09:44
Block: 722665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550129 RingCT/type: yes/0
Extra: 01fbedbae654ad5f1d8a636a648df87bdc6f9ef84d7e8283b37c151ae4000f75eb021100000002b3164c24000000000000000000

1 output(s) for total of 2.474632672000 dcy

stealth address amount amount idx
00: 282a3fdcb07512a8899da1639cab136b0a0d3c85b73bd093de0d92a57a8e36be 2.474632672000 1167608 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": 722675, "vin": [ { "gen": { "height": 722665 } } ], "vout": [ { "amount": 2474632672, "target": { "key": "282a3fdcb07512a8899da1639cab136b0a0d3c85b73bd093de0d92a57a8e36be" } } ], "extra": [ 1, 251, 237, 186, 230, 84, 173, 95, 29, 138, 99, 106, 100, 141, 248, 123, 220, 111, 158, 248, 77, 126, 130, 131, 179, 124, 21, 26, 228, 0, 15, 117, 235, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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