Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a8cb7854ae195850a73b60bfb2a23f41ad89785637fdb3fb0c5e43cb93a3816

Tx prefix hash: 1a5320e84dddd9a552f453c92ae148c50d58cc88f4094a81d6ad81f38f424180
Tx public key: 720af3eadb3aaee5dd355a1130936cc5fa42956c57884c56c3ed01bbb8aeba17
Timestamp: 1693056146 Timestamp [UCT]: 2023-08-26 13:22:26 Age [y:d:h:m:s]: 01:143:07:54:07
Block: 834349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363791 RingCT/type: yes/0
Extra: 01720af3eadb3aaee5dd355a1130936cc5fa42956c57884c56c3ed01bbb8aeba17021100000005faf35c9c000000000000000000

1 output(s) for total of 1.055493317000 dcy

stealth address amount amount idx
00: 1a7aa5768ca106933df1ed0bd0b550c45c89b0e6556e69379c76bb2e1daf87b8 1.055493317000 1286839 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": 834359, "vin": [ { "gen": { "height": 834349 } } ], "vout": [ { "amount": 1055493317, "target": { "key": "1a7aa5768ca106933df1ed0bd0b550c45c89b0e6556e69379c76bb2e1daf87b8" } } ], "extra": [ 1, 114, 10, 243, 234, 219, 58, 174, 229, 221, 53, 90, 17, 48, 147, 108, 197, 250, 66, 149, 108, 87, 136, 76, 86, 195, 237, 1, 187, 184, 174, 186, 23, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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