Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca84e85c7fc82c6d527513b354bb6df644369e698dc4241d7da4f46ccf638164

Tx prefix hash: fcadc7037149081a6f5f01237efd54c71e5809a7a78339e9e4f71e4ca0303ef5
Tx public key: 3c3d7f6539326a7b8d5f1d4683c3eaef5f2a94af32a0ff7c3321a74b525230e9
Timestamp: 1687418765 Timestamp [UCT]: 2023-06-22 07:26:05 Age [y:d:h:m:s]: 01:277:01:26:24
Block: 787690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459169 RingCT/type: yes/0
Extra: 013c3d7f6539326a7b8d5f1d4683c3eaef5f2a94af32a0ff7c3321a74b525230e902110000000375e3f0e9000000000000000000

1 output(s) for total of 1.506802015000 dcy

stealth address amount amount idx
00: 0d2116c66ccb8843d3caab7d7c3500739936ffdcdf313df7f6173fbf5eedc841 1.506802015000 1237765 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": 787700, "vin": [ { "gen": { "height": 787690 } } ], "vout": [ { "amount": 1506802015, "target": { "key": "0d2116c66ccb8843d3caab7d7c3500739936ffdcdf313df7f6173fbf5eedc841" } } ], "extra": [ 1, 60, 61, 127, 101, 57, 50, 106, 123, 141, 95, 29, 70, 131, 195, 234, 239, 95, 42, 148, 175, 50, 160, 255, 124, 51, 33, 167, 75, 82, 82, 48, 233, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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