Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f87d745a1f0cf48b2a2692cfd2ad0f6586a7a3a10e9e40b4674a0dbf3b171ee6

Tx prefix hash: cec1f5d3f052cdc9180739421059fa2ae5e71297fcf376064dd4654aa6f1968c
Tx public key: 385ca0158cc36dc70606393daeaf7eb9282c8fd53b71f28842b190ea8c8c6ddd
Timestamp: 1718291841 Timestamp [UCT]: 2024-06-13 15:17:21 Age [y:d:h:m:s]: 00:282:00:24:50
Block: 1043399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201533 RingCT/type: yes/0
Extra: 01385ca0158cc36dc70606393daeaf7eb9282c8fd53b71f28842b190ea8c8c6ddd02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f09521c9eaef49d031e55154386765e5a9ab4b5e2acaf1079328251b4086187 0.600000000000 1512544 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": 1043409, "vin": [ { "gen": { "height": 1043399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f09521c9eaef49d031e55154386765e5a9ab4b5e2acaf1079328251b4086187" } } ], "extra": [ 1, 56, 92, 160, 21, 140, 195, 109, 199, 6, 6, 57, 61, 174, 175, 126, 185, 40, 44, 143, 213, 59, 113, 242, 136, 66, 177, 144, 234, 140, 140, 109, 221, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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