Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65330561c40e4f1b62ab24edc21c3757c097b60839b5bcb98232ab388c8decd9

Tx prefix hash: 6ee101beefa2d020c769d90ec5e7d1ca3bd551a2df2871c72e464f3358f13034
Tx public key: 5c1275f37ebf7703c43c73b0f00deff279d8020febaa67c6eb6a3a2dbdb0c022
Timestamp: 1705274128 Timestamp [UCT]: 2024-01-14 23:15:28 Age [y:d:h:m:s]: 01:063:08:30:18
Block: 935452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306379 RingCT/type: yes/0
Extra: 015c1275f37ebf7703c43c73b0f00deff279d8020febaa67c6eb6a3a2dbdb0c0220211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cc72bc70bee037fe7a815e33b685497f0628c88f059e499c92e19d4a9476eb9 0.600000000000 1393468 of 15

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": 935462, "vin": [ { "gen": { "height": 935452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cc72bc70bee037fe7a815e33b685497f0628c88f059e499c92e19d4a9476eb9" } } ], "extra": [ 1, 92, 18, 117, 243, 126, 191, 119, 3, 196, 60, 115, 176, 240, 13, 239, 242, 121, 216, 2, 15, 235, 170, 103, 198, 235, 106, 58, 45, 189, 176, 192, 34, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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