Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 283250471a168fee61e1353224ceef3c837a732d26d50d7ed9f82c6d18bd1e88

Tx prefix hash: d86b176f0a38f887bfa22397fad5ed862217dacffd13c37446c4d3a808d0c373
Tx public key: 2298b42dc48d328031f974d145b9ce98b28303d3d91c72f3b7f22156b04e0804
Timestamp: 1731355841 Timestamp [UCT]: 2024-11-11 20:10:41 Age [y:d:h:m:s]: 00:138:04:58:19
Block: 1151601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98611 RingCT/type: yes/0
Extra: 012298b42dc48d328031f974d145b9ce98b28303d3d91c72f3b7f22156b04e08040211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d23f96dca5148b950a240a82a6bdeb519ae82183b713bbbbd2ca34461edc5f2b 0.600000000000 1637164 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": 1151611, "vin": [ { "gen": { "height": 1151601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d23f96dca5148b950a240a82a6bdeb519ae82183b713bbbbd2ca34461edc5f2b" } } ], "extra": [ 1, 34, 152, 180, 45, 196, 141, 50, 128, 49, 249, 116, 209, 69, 185, 206, 152, 178, 131, 3, 211, 217, 28, 114, 243, 183, 242, 33, 86, 176, 78, 8, 4, 2, 17, 0, 0, 0, 2, 31, 10, 83, 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