Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fe70992487857a32cdaed1f19121889a27f471b8970fd0a3994c69da0d2c67d

Tx prefix hash: 8ad21ead5f58af5aa4e6090ee40ee06bfa35ddc5ace08b21104a1e97a5f209d7
Tx public key: a9c8d0b578555e5d7ab87b01e4df57ad8efaa5ceb747f10972eae3a735a8a3e8
Timestamp: 1700501248 Timestamp [UCT]: 2023-11-20 17:27:28 Age [y:d:h:m:s]: 01:158:06:52:37
Block: 895899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374316 RingCT/type: yes/0
Extra: 01a9c8d0b578555e5d7ab87b01e4df57ad8efaa5ceb747f10972eae3a735a8a3e8021100000002679a8a81000000000000000000

1 output(s) for total of 0.659955568000 dcy

stealth address amount amount idx
00: 8d3c318b7f4bae3909f8a8e9673d507e266c55659ff3e71150b562e650f6cc60 0.659955568000 1352146 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": 895909, "vin": [ { "gen": { "height": 895899 } } ], "vout": [ { "amount": 659955568, "target": { "key": "8d3c318b7f4bae3909f8a8e9673d507e266c55659ff3e71150b562e650f6cc60" } } ], "extra": [ 1, 169, 200, 208, 181, 120, 85, 94, 93, 122, 184, 123, 1, 228, 223, 87, 173, 142, 250, 165, 206, 183, 71, 241, 9, 114, 234, 227, 167, 53, 168, 163, 232, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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