Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6de4b1b47507340516bc6cf74f01a6170bff77f47993e62ffc0ebce6966c419

Tx prefix hash: b1bee522ce7a830eb5c4ec81a8cfa3d6f65581d25d1fbf7e7d3c395df8515be6
Tx public key: cd2be8318cf8c83eaa04c922d4063b84ab2e9478a5b68c0b137bf79927894f09
Timestamp: 1672690088 Timestamp [UCT]: 2023-01-02 20:08:08 Age [y:d:h:m:s]: 02:105:11:50:26
Block: 666201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597081 RingCT/type: yes/0
Extra: 01cd2be8318cf8c83eaa04c922d4063b84ab2e9478a5b68c0b137bf79927894f0902110000000452542ceb000000000000000000

1 output(s) for total of 3.807145691000 dcy

stealth address amount amount idx
00: b480757ec25feddd5af158afe457de273dfcd38601b3f16390a9937602fe4b5b 3.807145691000 1107304 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": 666211, "vin": [ { "gen": { "height": 666201 } } ], "vout": [ { "amount": 3807145691, "target": { "key": "b480757ec25feddd5af158afe457de273dfcd38601b3f16390a9937602fe4b5b" } } ], "extra": [ 1, 205, 43, 232, 49, 140, 248, 200, 62, 170, 4, 201, 34, 212, 6, 59, 132, 171, 46, 148, 120, 165, 182, 140, 11, 19, 123, 247, 153, 39, 137, 79, 9, 2, 17, 0, 0, 0, 4, 82, 84, 44, 235, 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