Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e7b42265115034ce47c81f8587f39f4447c207c243ea79a98d9c1b68860be28

Tx prefix hash: c0830c966652aa308f9223b8c43982265d9874211deef0a281602b6642d9557b
Tx public key: b181af651c47f28874339273b4f8f35e24b02fcb21dcb98c238a8f4994d5da5b
Timestamp: 1717260734 Timestamp [UCT]: 2024-06-01 16:52:14 Age [y:d:h:m:s]: 00:360:00:21:31
Block: 1034858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257322 RingCT/type: yes/0
Extra: 01b181af651c47f28874339273b4f8f35e24b02fcb21dcb98c238a8f4994d5da5b021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3123fc62e743ab246251f73a149b33a732340aba5dbcbf112c783e92d24e0f6 0.600000000000 1503377 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": 1034868, "vin": [ { "gen": { "height": 1034858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3123fc62e743ab246251f73a149b33a732340aba5dbcbf112c783e92d24e0f6" } } ], "extra": [ 1, 177, 129, 175, 101, 28, 71, 242, 136, 116, 51, 146, 115, 180, 248, 243, 94, 36, 176, 47, 203, 33, 220, 185, 140, 35, 138, 143, 73, 148, 213, 218, 91, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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